Search results

Open source implementations as a baseline requirement for adequate implementation experience

Status: Open.

#614 In w3ctag/design-principles;

· csarven opened on May 19, 2026

New principle: API driven UI components

Status: Open.

#613 In w3ctag/design-principles;

· marcoscaceres opened on Mar 4, 2026

Guidance for readyState fields

Status: Open.

#605 In w3ctag/design-principles;

· LeaVerou opened on Nov 26, 2025

New principle: use "user attention" to prevent abuse of/by certain APIs

Status: Open.

#602 In w3ctag/design-principles;

· marcoscaceres opened on Oct 21, 2025

New principle: Content is accessible and internationalized by default

Status: Open.

#598 In w3ctag/design-principles;

· jyasskin opened on Sep 25, 2025

New principle: The web is stable

Status: Open.

#595 In w3ctag/design-principles;

· jyasskin opened on Sep 19, 2025

More guidance around making complex things possible vs simple things easy

Status: Open.

#582 In w3ctag/design-principles;

· LeaVerou opened on Aug 6, 2025

Should native elements use slots?

Status: needs consensusWe're discussing this but do not yet have consensus.We're discussing this but do not yet have consensus.

Topic: HTML

Status: Open.

#581 In w3ctag/design-principles;

· LeaVerou opened on Jul 31, 2025

New principle: Guidance for URL patterns and URL templates?

Status: Open.

#579 In w3ctag/design-principles;

· LeaVerou opened on Jul 23, 2025

Sharpen point about promises and permissions

Status: Open.

#578 In w3ctag/design-principles;

· martinthomson opened on Jul 16, 2025

New CSS principle: Describe when 'auto' is an appropriate property value

Status: Open.

#568 In w3ctag/design-principles;

· jyasskin opened on Apr 10, 2025

New principle: When handling extensibility by having clients ignore unknown parameters, consider a "critical" list

Status: Open.

#560 In w3ctag/design-principles;

· jyasskin opened on Feb 26, 2025