谈谈网页排版与Web标准

Web for All

• Understand the gaps and requirements for text layout features
• Fill in the gaps, help developers learn new features, and create content in their own language

Language matrix

例：避头尾

Typographic features

• Vertical text
• Bidirectional text
• Characters
• Fonts
• Font styles
• Glyph control
• Cursive text
• Transforms
• Boundaries
• Text decoration
• Quotations
• Inline annotation
• Numbers, dates ...
• Otder inline
• Line breaking
• Hyphenation
• Align, justify ...
• Letter/word space
• Lists, counters
• Styling initials
• Baselines
• Other paragraph
• Page layout
• Notes, footnotes
• Page no.s, heads ...
• Forms, interaction
• Other pagination

jlreq

Other requirement documents

• alreq
• clreq
• klreq
• More in the pipeline...

Language enablement index

Spec reviews

specdev

String metadata

String metadata

However...

Contributing to the Web

• Explainer
• Find the right community/group
• Web IDL for APIs
• Step-by-step algorithms
• GitHub, Markdown, respec, bikeshed, etc.
• Get an early review w3ctag/design-reviews
• Write web-platform-tests (WPT) tests

Explainer

• What problem are you trying to solve?
• keep track of and make a note of alternatives which have been considered
• Be clear about the end-user need, first and foremost.
• The explainer is for everyone to read
• Check out the TAG documentation

Find the right community/group

You need to sell your idea

• Be open!
• Present your proposal in conferences, meetups, W3C TPAC
• W3C Community Groups: create your own (for big ideas, like WASM, WebGPU) or use WICG
• Find implementers
• Ask the W3C Staff for help in finding the right individuals to talk to

Web IDL for APIs

• interface definition language to describe API for the Web
• Best is to look at existing examples, like Payment Request API, Fetch, Intersection Observer
• Make sure you know JavaScript

specification

Step by step algorithm

Write the specification for implementers

The PaymentRequest(methodData, details, options) constructor MUST act as follows:

1. If the current settings object's responsible document is not allowed to use the "payment" feature, then throw a "SecurityError" DOMException.
2. Establish the request's id:
   1. If details.id is missing, add an id member to details and set its value to a UUID [RFC4122].
3. Let serializedMethodData be an empty list.
4. Process payment methods:
   1. If the length of the methodData sequence is zero, then throw a TypeError, optionally informing the developer that at least one payment method is required.

Tools

• Use GitHub to interact with your audience
• Explainer is written in markdown
• Specification should be written in respec or bikeshed

TAG review

• Get it as early as possible (complete explainer, draft of a spec). Do not wait!
• It's a two way communication
• Raise an issue w3ctag/design-reviews
• Check other issues for example

Write tests

• Unless you have tests, your feature won't get implementers traction
• web-platform-tests is the de facto Test project for the Web
• Consider adding WebDriver in your proposal if needed

W3C Process

Working Draft (WD)

Design phase

Candidate Recommendation (CR)

Testing phase

Recommendation (REC)

Maintainance phase

谢谢！

问题?