惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

N
News and Events Feed by Topic
GbyAI
GbyAI
博客园 - Franky
宝玉的分享
宝玉的分享
Blog — PlanetScale
Blog — PlanetScale
Google DeepMind News
Google DeepMind News
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
人人都是产品经理
人人都是产品经理
Microsoft Azure Blog
Microsoft Azure Blog
The Register - Security
The Register - Security
腾讯CDC
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
I
InfoQ
The Cloudflare Blog
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
Engineering at Meta
Engineering at Meta
MongoDB | Blog
MongoDB | Blog
有赞技术团队
有赞技术团队
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
F
Full Disclosure
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
Vercel News
Vercel News
博客园 - 【当耐特】
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
S
Schneier on Security
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
Project Zero
Project Zero
量子位
M
MIT News - Artificial intelligence
Stack Overflow Blog
Stack Overflow Blog
C
Cyber Attacks, Cyber Crime and Cyber Security
美团技术团队
Attack and Defense Labs
Attack and Defense Labs
C
Cybersecurity and Infrastructure Security Agency CISA
T
The Blog of Author Tim Ferriss
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
T
Troy Hunt's Blog
Google Online Security Blog
Google Online Security Blog
罗磊的独立博客
P
Proofpoint News Feed
Schneier on Security
Schneier on Security
Spread Privacy
Spread Privacy
S
SegmentFault 最新的问题
L
LINUX DO - 最新话题
Simon Willison's Weblog
Simon Willison's Weblog
爱范儿
爱范儿
博客园 - 聂微东
A
About on SuperTechFans
PCI Perspectives
PCI Perspectives
D
Docker

Recent Commits to design-principles:main

Event names should use the present tense (#592) Disambiguate when to add global event handlers (#612) · w3ctag/design-principles@41fee41 Handle non-fully-active documents (#597) chore: fix bikeshed warning about multiple definitions of the <a> ele… · w3ctag/design-principles@6ec7e11 Guidance on extensibility patterns: main spec revision vs registries … Un-escape ampersands in a URL to avoid a bikeshed bug. · w3ctag/design-principles@031a3de Trim trailing whitespace. Rewrite the "removing features" section, incorporating "Support Exist… · w3ctag/design-principles@62fc770 Replace asking for users for consent with designing for user intent (… Clarify when details should go on events vs targets (#585) · w3ctag/design-principles@79c2b78 Avoid abbreviations generally (#600) · w3ctag/design-principles@9fc15ba Add principles for task sources (#590) · w3ctag/design-principles@444a329 Clean up link-defaults. · w3ctag/design-principles@993e58e Remove trailing whitespace (#593) · w3ctag/design-principles@98f4a02 Ignore index.html at the root. (#586) Fix example in Keep attributes in sync (#591) · w3ctag/design-principles@afb192e Remove notion of asking for consent to reveal AT use (#589) · w3ctag/design-principles@c35b9cd Reference HTTP WG style guide (#587) · w3ctag/design-principles@81e3ff2 Add 'Choose the Appropriate WebIDL Construct for Data and Behavior' (…
Update ethical-web-principles links and bibrefs (#601) · w3ctag/design-principles@63b43c9
csarven · 2025-10-21 · via Recent Commits to design-principles:main

@@ -14,7 +14,7 @@ Former Editor: Lea Verou, Invited Expert, https://lea.verou.me, w3cid 52258

1414

Former Editor: Sangwhan Moon, w3cid 42399, Google https://www.google.com/, https://sangwhan.com

1515

Former Editor: Domenic Denicola, Google https://www.google.com/, https://domenic.me/, d@domenic.me

1616

Former Editor: Travis Leithead, Microsoft, travil@microsoft.com

17-

Abstract: This document contains a set of design principles to be used when designing web platform technologies. These principles have been collected during the Technical Architecture Group's discussions in <a href="https://github.com/w3ctag/design-reviews/">reviewing</a> developing specifications, and build upon the Ethical Web Principles [[ETHICAL-WEB]]. We encourage specification designers to read this document and use it as a resource when making design decisions.

17+

Abstract: This document contains a set of design principles to be used when designing web platform technologies. These principles have been collected during the Technical Architecture Group's discussions in <a href="https://github.com/w3ctag/design-reviews/">reviewing</a> developing specifications, and build upon the Ethical Web Principles [[ethical-web-principles]]. We encourage specification designers to read this document and use it as a resource when making design decisions.

1818

Default Biblio Status: current

1919

Markup Shorthands: markdown on

2020

Boilerplate: feedback-header off

@@ -53,7 +53,7 @@ urlPrefix: https://www.rfc-editor.org/rfc/rfc9110.html; spec: rfc9110

5353

<h2 id="basic-principles">Principles behind design of Web APIs</h2>

54545555

The Design Principles are directly informed by the ethical framework

56-

set out in the Ethical Web Principles [[ETHICAL-WEB]].

56+

set out in the Ethical Web Principles [[ethical-web-principles]].

5757

These principles provide concrete practical advice

5858

in response to the higher level ethical responsibilities

5959

that come with developing the web platform.

@@ -68,7 +68,7 @@ be sure to understand and document the user need that the API aims to address.

68686969

[The internet is for end users](https://tools.ietf.org/html/rfc8890):

7070

any change made to the web platform has the potential to

71-

[affect vast numbers of people](https://www.w3.org/2001/tag/doc/ethical-web-principles/#allpeople),

71+

[affect vast numbers of people](https://www.w3.org/TR/ethical-web-principles/#allpeople),

7272

and may have a profound impact on any person's life. [[RFC8890]]

73737474

User needs come before the needs of web page authors,

@@ -86,8 +86,8 @@ and theoretical concerns reflect underlying needs of all of these groups.

86868787

See also:

888889-

* [The web should not cause harm to society](https://www.w3.org/2001/tag/doc/ethical-web-principles/#noharm)

90-

* [The web must enhance individuals' control and power](https://www.w3.org/2001/tag/doc/ethical-web-principles/#control)

89+

* [The web should not cause harm to society](https://www.w3.org/TR/ethical-web-principles/#noharm)

90+

* [The web must enhance individuals' control and power](https://www.w3.org/TR/ethical-web-principles/#control)

9191

* [[RFC8890]]

92929393

<h3 id="safe-to-browse">It should be safe to visit a web page</h3>

@@ -100,7 +100,7 @@ The Web is named for its hyperlinked structure.

100100

In order for the web to remain vibrant,

101101

users need to be able to expect that merely visiting any given link

102102

won't have implications for the security of their computer,

103-

or for any essential aspects of their [privacy](https://www.w3.org/2001/tag/doc/ethical-web-principles/#privacy).

103+

or for any essential aspects of their [privacy](https://www.w3.org/TR/ethical-web-principles/#privacy).

104104105105

For example, an API that allows any website to

106106

[detect the use of assistive technologies](#do-not-expose-use-of-assistive-tech)

@@ -143,7 +143,7 @@ Users depend on trusted user interfaces

143143

such as the address bar, security indicators and permission prompts,

144144

to understand who they are interacting with and how.

145145

These trusted user interfaces must be able to be designed in a way

146-

that enables users to trust [and verify](https://www.w3.org/2001/tag/doc/ethical-web-principles/#verify)

146+

that enables users to trust [and verify](https://www.w3.org/TR/ethical-web-principles/#verify)

147147

that the information they provide is genuine,

148148

and hasn't been spoofed or hijacked by the website.

149149

@@ -163,7 +163,7 @@ In the context of fulfilling a user need,

163163

a web page may want to make use of a feature

164164

that has the potential to cause harm.

165165

Features that have this potential for harm should be designed such that people can give

166-

[meaningful consent](https://www.w3.org/2001/tag/doc/ethical-web-principles/#control) for that feature to be used,

166+

[meaningful consent](https://www.w3.org/TR/ethical-web-principles/#control) for that feature to be used,

167167

and that they can refuse consent effectively.

168168169169

In order to give *meaningful consent*, the user must:

@@ -210,7 +210,7 @@ no location information is available to the Web page.

210210211211

See also:

212212213-

* [The web is secure, and respects people's privacy](https://www.w3.org/2001/tag/doc/ethical-web-principles/#privacy)

213+

* [The web is secure, and respects people's privacy](https://www.w3.org/TR/ethical-web-principles/#privacy)

214214

* [Consent Principles](https://www.w3.org/TR/privacy-principles/#consent-principles)

215215

* [Permissions](https://www.w3.org/TR/permissions/)

216216

@@ -258,7 +258,7 @@ a Web page may be viewed on virtually any consumer computing device

258258

at a very wide range of screen sizes,

259259

may be used to generate printed media,

260260

and may be interacted with in a large number of different ways.

261-

New features should match the [existing flexibility](https://www.w3.org/2001/tag/doc/ethical-web-principles/#render)

261+

New features should match the [existing flexibility](https://www.w3.org/TR/ethical-web-principles/#render)

262262

of the web platform.

263263264264

<div class="note">

@@ -719,10 +719,10 @@ Some people use [private browsing mode](https://www.w3.org/2001/tag/doc/private-

719719

to protect their own personal safety.

720720

Because of this, the fact that someone is using private browsing mode

721721

may be [sensitive information](https://www.w3.org/TR/security-privacy-questionnaire/#sensitive-data) about them.

722-

This information may [harm](https://www.w3.org/2001/tag/doc/ethical-web-principles/#noharm) people

722+

This information may [harm](https://www.w3.org/TR/ethical-web-principles/#noharm) people

723723

if it is revealed to a web site controlled by others who have power over them

724724

(such as employers, parents, partners,

725-

or [state actors](https://www.w3.org/2001/tag/doc/ethical-web-principles/#expression)).

725+

or [state actors](https://www.w3.org/TR/ethical-web-principles/#expression)).

726726727727

Given such dangers,

728728

websites should not be able to detect that private browsing mode is engaged.

@@ -750,7 +750,7 @@ without revealing that private browsing mode is engaged.

750750751751

See also:

752752753-

* [Security and privacy are essential](https://www.w3.org/2001/tag/doc/ethical-web-principles/#privacy)

753+

* [Security and privacy are essential](https://www.w3.org/TR/ethical-web-principles/#privacy)

754754

* [What data does this specification expose to an origin?](https://www.w3.org/TR/security-privacy-questionnaire/#underlying-platform-data)

755755

* [[#private-browsing-mode]]

756756

@@ -803,16 +803,16 @@ See also:

803803

Make sure that your API doesn't provide a way

804804

for authors to detect that a user is using assistive technology.

805805806-

[The web platform must be accessible to people with disabilities.](https://www.w3.org/2001/tag/doc/ethical-web-principles/#allpeople)

806+

[The web platform must be accessible to people with disabilities.](https://www.w3.org/TR/ethical-web-principles/#allpeople)

807807

If a site can detect that a user is using an assistive technology,

808808

that site can deny or restrict the user's access to the services it provides.

809809810810

People who make use of assistive technologies

811-

are often [vulnerable members of society](https://www.w3.org/2001/tag/doc/ethical-web-principles/#noharm);

811+

are often [vulnerable members of society](https://www.w3.org/TR/ethical-web-principles/#noharm);

812812

their use of assistive technologies is [sensitive information](https://www.w3.org/TR/security-privacy-questionnaire/#sensitive-data) about them.

813813

If an API provides access to this information,

814814

this sensitive information may be revealed to others

815-

(including [state actors](https://www.w3.org/2001/tag/doc/ethical-web-principles/#expression))

815+

(including [state actors](https://www.w3.org/TR/ethical-web-principles/#expression))

816816

who may wish them harm.

817817818818

Sometimes people propose features which aim to improve the user experience

@@ -837,7 +837,7 @@ which don't reveal the use of assistive technology.

837837

See also:

838838839839

* [Web Technology Accessibility Guidelines](https://w3c.github.io/apa/fast/)

840-

* [Security and privacy are essential](https://www.w3.org/2001/tag/doc/ethical-web-principles/#privacy)

840+

* [Security and privacy are essential](https://www.w3.org/TR/ethical-web-principles/#privacy)

841841

* [What data does this specification expose to an origin?](https://www.w3.org/TR/security-privacy-questionnaire/#underlying-platform-data)

842842843843

<h3 id="require-user-activation">Require user activation for powerful APIs</h3>

@@ -3206,7 +3206,7 @@ the user experience will suffer.

32063206

(This problem is even more pronounced on low-powered devices,

32073207

which are more likely to be used by disadvantaged or marginalized users.

32083208

Remember,

3209-

[the web is for all people](https://www.w3.org/2001/tag/doc/ethical-web-principles/#allpeople).)

3209+

[the web is for all people](https://www.w3.org/TR/ethical-web-principles/#allpeople).)

3210321032113211

Therefore,

32123212

APIs which would often block the main thread if used as intended