Issues

• New principle: When should events bubble by default?

  w3ctag/design-principles#618 · Filter by author LeaVerou opened on Jul 30, 2026

• Broken links in Web Platform Design Principles

  w3ctag/design-principles#617 · Filter by author dontcallmedom-bot opened on Jul 22, 2026

• Question: can we better define the intention of the "disable scripting" user preference

  Agenda+
  w3ctag/design-principles#619 · Filter by author noamr opened on Jul 21, 2026
  15

  

• Open source implementations as a baseline requirement for adequate implementation experience

  w3ctag/design-principles#614 · Filter by author csarven opened on May 19, 2026
  5

• New principle: API driven UI components

  w3ctag/design-principles#613 · Filter by author marcoscaceres opened on Mar 4, 2026
  3

• Guidance for readyState fields

  w3ctag/design-principles#605 · Filter by author LeaVerou opened on Nov 26, 2025

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

  w3ctag/design-principles#602 · Filter by author marcoscaceres opened on Oct 21, 2025
  1

• New principle: Content is accessible and internationalized by default

  w3ctag/design-principles#598 · Filter by author jyasskin opened on Sep 25, 2025

• New principle: The web is stable

  w3ctag/design-principles#595 · Filter by author jyasskin opened on Sep 19, 2025

• More guidance around making complex things possible vs simple things easy

  w3ctag/design-principles#582 · Filter by author LeaVerou opened on Aug 6, 2025

• Should native elements use slots?

  Status: needs consensusTopic: HTML
  w3ctag/design-principles#581 · Filter by author LeaVerou opened on Jul 31, 2025
  12

• New principle: Guidance for URL patterns and URL templates?

  w3ctag/design-principles#579 · Filter by author LeaVerou opened on Jul 23, 2025
  2

• Sharpen point about promises and permissions

  w3ctag/design-principles#578 · Filter by author martinthomson opened on Jul 16, 2025
  1

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

  w3ctag/design-principles#568 · Filter by author jyasskin opened on Apr 10, 2025

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

  w3ctag/design-principles#560 · Filter by author jyasskin opened on Feb 26, 2025
  1

• Add ids to the examples, to make deep links more stable

  w3ctag/design-principles#557 · Filter by author martinthomson opened on Feb 21, 2025

• Synchronous layout-forcing APIs are not covered by any guideline

  w3ctag/design-principles#556 · Filter by author xiaochengh opened on Feb 19, 2025

• JSON keys are incompatible with Web IDL dictionaries

  w3ctag/design-principles#554 · Filter by author annevk opened on Feb 12, 2025
  4

• New principle: Sourcing models and compute for inference

  w3ctag/design-principles#551 · Filter by author martinthomson opened on Feb 6, 2025
  3

• Update Trusted UI principle with Chromium's spoofing and clickjacking guidance

  w3ctag/design-principles#548 · Filter by author jyasskin opened on Jan 13, 2025
  1

  

• New principle: Don't invent something new just because the existing thing isn't perfect

  w3ctag/design-principles#539 · Filter by author martinthomson opened on Dec 9, 2024
  2

• New principle: Write [Symbol.dispose]() and [Symbol.asyncDispose]() methods when appropriate

  w3ctag/design-principles#537 · Filter by author jyasskin opened on Dec 6, 2024
  4

• Consider adding publishers into the Priority of Constituencies

  w3ctag/design-principles#535 · Filter by author jyasskin opened on Dec 6, 2024
  3

• Additional examples around element overloading

  Topic: HTML
  w3ctag/design-principles#533 · Filter by author LeaVerou opened on Dec 4, 2024

• New principle: Avoid introducing mode errors

  Topic: Meta
  w3ctag/design-principles#532 · Filter by author LeaVerou opened on Dec 4, 2024