|
8 | 8 | <meta content="Bikeshed version b25686b9f, updated Fri Mar 14 14:15:20 2025 -0700" name="generator">
|
9 | 9 | <link href="https://www.w3.org/TR/design-principles/" rel="canonical">
|
10 | 10 | <link href="https://www.w3.org/2008/site/images/favicon.ico" rel="icon">
|
11 |
| - <meta content="2dacfeaf2074be60df7dbdf9f51f0268922770cf" name="revision"> |
| 11 | + <meta content="e10b073ce0c8064fd1479b80234df8bc62835196" name="revision"> |
12 | 12 | <meta content="dark light" name="color-scheme">
|
13 | 13 | <link href="https://www.w3.org/StyleSheets/TR/2021/dark.css" media="(prefers-color-scheme: dark)" rel="stylesheet" type="text/css">
|
14 | 14 | <style>
|
|
702 | 702 | <div class="head">
|
703 | 703 | <p data-fill-with="logo"><a class="logo" href="https://www.w3.org/"> <img alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2021/logos/W3C" width="72"> </a> </p>
|
704 | 704 | <h1 class="p-name no-ref" id="title">Web Platform Design Principles</h1>
|
705 |
| - <p id="w3c-state"><a href="https://www.w3.org/standards/types/#ED">Editor’s Draft</a>, <time class="dt-updated" datetime="2025-04-30">30 April 2025</time></p> |
| 705 | + <p id="w3c-state"><a href="https://www.w3.org/standards/types/#ED">Editor’s Draft</a>, <time class="dt-updated" datetime="2025-05-16">16 May 2025</time></p> |
706 | 706 | <details open>
|
707 | 707 | <summary>More details about this document</summary>
|
708 | 708 | <div data-fill-with="spec-metadata">
|
@@ -1154,14 +1154,22 @@ <h3 class="heading settled" data-level="1.8" id="removing-features"><span class=
|
1154 | 1154 | they are also defined by how content uses those features.</p>
|
1155 | 1155 | <h3 class="heading settled" data-level="1.9" id="leave-the-web-better"><span class="secno">1.9. </span><span class="content">Leave the web better than you found it</span><a class="self-link" href="#leave-the-web-better"></a></h3>
|
1156 | 1156 | <p>As you add new capabilities to the web platform,
|
1157 |
| -do so in a way that improves the overall platform, |
1158 |
| -for example its security, privacy or accessibility characteristics.</p> |
| 1157 | +do so in a way that improves the overall platform.</p> |
1159 | 1158 | <p>The existence of a defect in one part of the platform
|
1160 | 1159 | must not be used to excuse an addition or extension to the defect,
|
1161 |
| -which would further decrease the overall platform quality. |
| 1160 | +which would further decrease the overall platform quality.</p> |
| 1161 | + <p>Consistency with existing problematic design patterns |
| 1162 | +is not a good reason to propagate those patterns |
| 1163 | +in newly specified Web APIs or platform features. |
1162 | 1164 | Where possible, build new web capabilities that improve the overall platform quality
|
1163 |
| -by mitigating existing defects. |
1164 |
| -Do not degrade existing capabilities without good reason.</p> |
| 1165 | +by mitigating existing defects.</p> |
| 1166 | + <p>Do not extend a platform feature that has known defects, |
| 1167 | +without considering how to address those defects. |
| 1168 | +It is not necessary to completely fix existing problems, |
| 1169 | +but some attempt to address flaws is expected |
| 1170 | +when extending a feature with known issues. |
| 1171 | +This way, new or increased usage does not result in |
| 1172 | +increasing the harm that the defect might cause.</p> |
1165 | 1173 | <p>Parts of the web platform evolve independently.
|
1166 | 1174 | Issues that are present with a certain web technology now may be fixed in a subsequent iteration.
|
1167 | 1175 | Duplicating these issues makes fixing them more difficult.
|
|
0 commit comments