CSS WG Blog front page

This is a page from the Cascading Style Sheets Working Group Blog. Some other places to find information are the “current work” page, the www-style mailing list, the Future of CSS syndicator, and the issue list on Github.

Do you want to know how the CSS WG works? Fantasai has written about:csswg, An Inside View of the CSS Working Group at W3C.

Minutes and Resolutions 2010-09-15

• Peter set up an agenda template for TPAC on the wiki.
• Reviewed status of CSS2.1 issues.
• Resolved: Accept fantasai’s proposed text for CSS2.1 Issue 173 with option B
• Resolved: Accept proposal for CSS2.1 Issue 203
• Resolved: In CSS Values Level 3, mark min() and max() as at-risk, and mark percentages in min() and max() as at-risk.
• Reviewed Tab’s proposal for counter style definitions.
• Discussed how to get implementation reports for CSS2.1 test suite

Full minutes

Minutes and Resolutions 2010-09-08

• Resolved: Accept Bert’s changes for CSS2.1 Issue 121 with slight edit suggested by dbaron in the minutes.
• Resolved: Accept fantasai’s proposal for CSS2.1 Issue 158
• Reviewed proposal for CSS2.1 Issue 158; more edit work needed.
• Resolved: Accept fantasai’s proposal for CSS2.1 Issue 172
• Resolved: Accept fantasai’s proposal for CSS2.1 Issue 187
• Resolved: Accept updated wording for CSS2.1 Issue 187
• Reviewed CSS2.1 Issue 197: need test case results and proposed text.
• Reviewed CSS2.1 Issue 199

Full minutes

CSS3 Text Working Draft Published

The CSS Working Group has published a new draft of the CSS Text Module Level 3 specification. This module covers, among other things:

• White space processing
• Line breaking
• Justification
• Text decoration

Derived from the early CSS Internationalization drafts, one of its primary goals is to provide key features needed to correctly typeset languages from around the world. Please, review the draft and comment! We especially welcome feedback from the Indic, Southeast Asian, and Arabic script communities, as their input has been noticeably missing. Instructions for sending feedback are in the status section.

The CSS Working Group needs you!

This message from Daniel Glazman, with his CSS WG Co-chair hat on:

Yes, we need you. CSS 2.1 is a complex specification, and it has roughly 20,000 HTML4 and XHTML1 tests in its Test Suite. To make the document move from Candidate Recommendation to Proposed Recommendation, we need to show that each and every test in that Test Suite is passed by at least two different implementations. And that’s where you can help:

If you have a few spare cycles and are able to test a few hundreds or thousands of the tests in the Test Suite with the latest version (see below) of Opera, Firefox4beta, IE or WebKit, please help us.

The results are aggregated into a database. Thanks a lot for your help!

Builds to be tested (and only those ones please):

• Mozilla Firefox 4 Beta
• Apple Safari 5.02
• Microsoft Internet Explorer 9 Beta
• Opera pre-10.70 Snapshot 9046

Minutes and Resolutions Oslo F2F Wednesday 2010-08-25: Fonts, UI, Writing Modes, i18n, Template Layout, Values and Units

Testing and PR

John Daggett from Mozilla took Microsoft’s marketing dept. to task for publishing PR articles using test results from unreviewed Microsoft tests “that wouldn’t even pass Microsoft’s internal review” while implying that they were accepted by W3C.

Advice for the future use of test results in marketing materials include:

• Giving some kind of advance notification about the tests and the intent to publish test results based on them to other browser vendors, and promptly fixing any reported test errors.
• Using only reviewed tests for marketing purposes.
• Just generally making a good faith effort when publishing test results comparing products.

Fonts

jdaggett reviewed the font-variant-* features. Comments included:

• font-variant-ligatures should note that it doesn’t affect required ligatures.
• Many members of the WG are (still) concerned about the use of numeric alternate glyph selection in font-variant-alternates in a way that does not tie the numbers to specific fonts, the problem being that the numbered options would be applied to fallback fonts, resulting in unexpected glyph selections. jdaggett protested that this isn’t a problem in reality while Adobe asserted that it will become more and more of a problem over time as use of advanced font technology increases. Several alternatives were proposed:
  • Allowing numeric glyph selection only via @font-face.
  • Using a functional notation to tie that selection to a specific font family.
  • Using an at-rule to match named identifiers to pairs of numeric selections and font-family names. (This has the added benefit of giving the author an obvious way to note what such numbers mean to any future maintainers.)
• Suggestion to have petite-caps fall back to small-caps. jdaggett to mark this in the spec as an issue.
• Discussed jdaggett’s proposal to CSSify font-feature-settings syntax by using idents and functional notation in place of strings. Bert noted that this may conflict with things like attr(), so the WG suggested prefixing each value with ot-. Also discussed error-handling.
• Noted that font-language-override‘s values are OT lang codes, not ISO lang codes. One suggestion was to accept ISO lang codes as idents and OT lang codes as strings.
• Resolved: Publish new CSS3 Fonts Working Draft.
• Some discussion about font family names inside fonts and how to make use of them across platforms.

Writing Modes

• Discussed various solutions for dealing with vertical writing modes and the resulting directional transformations.
• Several strongly against :ttb solution, since it is supposedly a pseudo-class, but is selecting a property of the UA, not of the element. Media Queries are seen as a more appropriate place to detect features of the UA environment.
• The WG favors alternate style sheets for writing mode switching, since they give the most versatile solution. Some guidelines are needed to allow standardized tagging of alternate styles. But once those are in place, EPUB can choose what switches it needs, similar to defining a microformat. And other products can similarly define standardized switches for other things.
• Some comments made about detecting vertical writing support, but nothing definite.
• Some discussion of the cascading problems with margin-start/end/before/after. And also the similar but somewhat different case of margin-outside/inside, whose directions must be computed as pages are laid out and cannot be resolved during the cascade.
• ReResolved: Physical directions stay physical: margin-left will always refer to the left side, not the top or right side based on physical directions.

#rrggbbaa

Resolved: Add #rrggbbaa to CSS4 Color.

CSS3 UI and UI Selectors

• Tantek is going through the old Candidate Recommendation and will be re-issuing an Last Call Working Draft that removes all unimplemented features and adds related features that have two+ implementations (such as ointer-events and overflow-x/overflow-y).
• There was a suggestion to extract the selectors in this draft into a standalone UI Selectors module.
• dbaron wrote a list of 5 requirements for ::selection: WG agrees with all of them; problem is now a matter of defining a model that accommodates all of them.

i18n: list-styles and Indic layout

Discussed request for list-style: auto: Authors can already map list styles to languages with :lang(), so this feature does not seem necessary. Also, it would require a great deal of research to specify adequately. The CSSWG would consider adding the feature described if someone else did the necessary research to draw up an exhaustive table mapping lang codes to list-style-types and the Internationalization Working Group approved it.

A new group at W3C is planning to draw up requirements for Indic layout, similar to the JLTF efforts.

CSS Template Layout

Discussed Hyatt’s proposal

to alter syntax to make prefixing easier (which has the side effect of making the style sheet easier to understand, especially for someone unfamiliar with the Template module). The WG votes to add slot() notation to the ‘position’ values and to wrap the template strings in functional notation rather than add a new property as in Hyatt’s proposal.

CSS3 Values and Units and calc()

Proposed to move CSS3 Values and Units to Candidate Recommendation to get calc() out. Starting by trimming any unfinished features and drawing up an at-risk list in prepartion for Last Call. This would mean: dropping fr and gr units, since they aren’t standalone units anyway; and marking vh, vw, vm, and min() and max() at-risk.

Full minutes

Minutes and Resolutions Oslo F2F Tuesday 2010-08-24: GCPM, MQ, Flexbox, Multicol, box-shadow, Publications, Future F2Fs

CSS3 Generated Content for Paged Media

Håkon would like to prepare the module for CR. Several people feel many of the features would be better placed in more appropriate modules, e.g. hyphenation to CSS3 Text. Some features may be underdefined. But nobody objected to any of the features fundamentally.

Wrt hyphenation:

• Discussed hyphenate-resource property and use of local dictionaries instead of specified ones.
• Discussed hyphenate-character property; it seems it should be able to accept a second character for languages where a second hyphenation character is used after the line break.
• Discussed whether control is needed to prevent hyphenation on the last line of a page: plan to recommend the UA to prevent such hyphenation, add a control only if market determines one is needed.
• Discussed possible use cases for specifying the hyphenation language, but none seemed needed—the hyphenation language pretty much always matches the content language.
• Proposed to replace hyphenate-resource property with an at-rule that maps language tags to hyphenation resources, since hyphenation resources need to be specified per language, but not per element. E.g.

  @hyphenate-resource {
  en-US: url(en-US.hy);
  en:    url(en-GB.hy);
  fr:    url(fr.hy);
  }

  This could also allow more intelligent lang-code→dictionary mapping than using :lang() selectors and a property.

Reviewed several other features including:

• cmyk() colors, which were proposed to rename device-cmyk() since they do not use a device-specific color profile.
• bookmarks, which should have more examples added to explain their usage
• line-box-contain, which needs more investigation

Hit Testing

• Plan to add pointer-events to UI module edited by Tantek.
• Correct default behavior uncertain, needs testcases and investigation.
• Resolved: Try and move AC review of charter forward, to get UI module in it and publish a LC asap.

Styling Attributes

Resolved: Publish CSS Styling Attributes as Candidate Recommendation.

Media Queries

• Reviewed status of test suite. Mostly waiting for another implementation to fix all its parsing errors; Mozilla passes all tests.
• Suggested to remove ‘color-index’; WG disagrees.
• Anne suggested a revision draft (Media Queries 3.1) to include serialization, media type deifnitions, making extensions by other specs easier, and maybe adding OM deifnitions. (WG considers copying media type definitions from CSS2.1 an editorial issue, so that part should be ok to fix in this version as well.)

Snapshot 2010

Resolved: 2010 Snapshot is 2007 Snapshot + Media Queries

Selector Serialization

• Need a Selectors 3.1 spec to define serialization and OM (not required for UAs without an OM).

Flexbox

• Discussed flex units and alternatives
• Resolved: ISSUE-138 Out-of-flow elements are treated as placeholders during flexbox construction, similar to tables.
• Resolved:ISSUE-140 ‘max-width/height’ on a flexbox child limits the size of the element; if this results in a shorter box than any other in its row, it is aligned as if box-align: before.
• Resolved: Baseline of a flexbox is the baseline of its first child. Note: this may be revisited based on use cases. ISSUE-141.
• Resolved: ISSUE-142 box-ordinal-group also reorders stacking order; i.e. it reorders the box tree.
• Resolved: ISSUE-143 Preferred width of flexbox children is ‘max-content’ not ‘fit-content’.
• ISSUE-144 Discussed distribution of negative space. Agreed that applying flex calculation with negative space is not ideal; alternatives to be investigated, including 1) ignoring flex when available space is negative 2) adopting TeX’s glue algorithms.
• Resolved: ISSUE-145 Contiguous non-replaced inline elements are wrapped into a single anonymous block. Atomic inline-level elements are individually wrapped into flexboxen.

Multi-Column Layout

• Resolved: Use border-collapse border-style behavior for column rules.
• Resolved: Column rules are not clipped by the multicol element horizontally; but are drawn to the height of the multicol element vertically.
• Resolved: Column rules are drawn “immediately below the border (above the background) of the multi-column element”.
• Resolved: ISSUE-129 Specified height does not disable column balancing unless content overflows.
• Resolved: Column-spanning elements have an effective column-span of 1 when occurring in an overflow column.

box-shadow

• Specification of box-shadow’s blur radius has been fixed.
• Resolved: Not altering stacking order of inset box-shadow to paint over content, since it would be a significant change from current implementations and would delay dropping prefixes. May add keyword to do this in the future.
• Resolved: Publish CSS3 Backgrounds and Borders as Candidate Recommendation.

F2F Scheduling

Tentatively scheduled: March 7-9 (MTW) 2010 in Mountain View and June 1-3 (WTF) 2010 in Tokyo

Full minutes

Minutes and Resolutions Oslo F2F Monday 2010-08-23: CSS2.1, CSSWG Charter, Viewport Sizing

CSS2.1 Issues

• Resolved: Bert’s proposal accepted for CSS2.1 Issue 129
• Resolved: Leave issue CSS2.1 Issue 144 officially undefined, add a note that it will be resolved in CSS3.
• Resolved: Proposal accepted for CSS2.1 Issue 172: caption width influences table width as if contained in a table-spanning cell. fantasai to tweak proposal as noted in minutes to be more clear.
• Resolved: For CSS2.1 Issue 183 change “@media and @import rules with unknown media types are treated as if the unknown media types are not present.” to “@media and @import rules with unknown media types (that are nonetheless valid identifiers) are treated as if the unknown media types are not present. If an @media rule contains a malformed media type (not an identifier) then the statement is invalid.” and add “Note: Media Queries supercedes this error handling.”
• Discussed CSS2.1 Issue 187 (bidi effects of atomic inline-level elements): agreed in principal with proposal but need clearer wording. [see Tuesday minutes].
• Resolved: Add a note about marker box stacking level for outside markers being undefined in CSS2.1 for CSS2.1 Issue 191.
• Resolved: For CSS2.1 Issue 192, accept change for first issue, replace “further content” with “content after the float” and “it” with “that content” for the second issue, third issue is invalid.
• Resolved: Proposal accepted for CSS2.1 Issue 194
• Resolved: For CSS2.1 Issue 195, proposal accepted with “even if either side is empty” appended. [see Tuesday minutes]
• Resolved: For CSS2.1 Issue 196, fix range of identifiers to include NBSP and exclude the control characters immediately below it.
• Resolved: For CSS2.1 Issue 197, edit spec to be clearer that when clear is applied to a run-in, it applies to the run-in itself if it displays as a block, and it applies to the block the run-in runs into if it displays as an inline.
• Resolved: For CSS2.1 Issue 198, clarify spec to say that run-in effectively causes a reordering of the source tree insofar as the formatting model is concerned, and the contents of the run-in are moved along with it. (This does not affect e.g. selectors, etc.)
• Resolved: Proposal accepted forCSS2.1 Issue 201 with “table wrapper box” as the term for the outer table box.
• Resolved: CSS2.1 Issues list is FROZEN in preparation for publication of a Last Call Working Draft.
• Resolved: CSS2.1 to progress from Last Call directly to Proposed Recommendation if it meets exit criteria.

CSS2.1 Test Suite

Discussed Release Candidate criteria, what happens to tests that are wrong, making implementation reports, and how we are measuring test coverage of the spec.

Test suite RC scheduled for September 15th; test errors must be fixed before RC. Implementation reports due 1 month after RC publication.

CSSWG Charter

• See also: current charter and its planning document.
• Reviewed contents of old charter, since we plan to copy most of it over.
• Reviewed current and expected status of modules, who is planning to work
  on what, and what priority they should have within the WG.
• Resolved: Move css3-marquee and css-mobile to low priority, send OMA liaison about this asking if they want to work on it.

First cut of 2010 module priorities (may be shuffled around later)

High Priority → Maintenance

• CSS2.1
• CSS Color Level 3
• CSS Namespaces
• CSS Styling Attributes
• Selectors Level 3

High priority

• CSS Snapshots
• CSS Backgrounds and Borders Level 3
• CSS UI Level 3
• CSS Fonts Level 3
• CSS Image Values Level 3
• CSS Multi-column Layout
• CSS 2D Transforms
• CSS Transitions
• CSS Values and Units
• Media Queries

Medium Priority

• CSS Box Model Level 3
• CSS Device Adaptation (@viewport proposal)
• CSS Flexbox
• CSS GCPM
• CSS Lists
• CSS Paged Media Level 3
• CSS Ruby
• CSS Template Layout
• CSS Text Level 3
• CSS Transforms 3D
• CSS Writing Modes Level 3 (vertical text)
• CSS Variables
• CSSOM
• CSSOM View

Low priority

• CSS Backgrounds and Borders Level 4
• CSS Filter Effects (applying SVG filters to CSS layouts)
• CSS Grid Positioning
• CSS Line Layout
• CSS Scoped Style Sheets
• CSS UI Level 4
• CSS Tables Level 3
• Selectors Level 4

Not Yet Prioritized

• Media Queries 3 Revision 1 (adding OM and serialization definitions)
• Selectors Level 3 Revision 1 (adding OM and serialization definitions)

Viewport Meta and CSS Syntax

Reviewed Rune’s proposal for an @viewport rule to set the size of the inital containing block independently of the viewport itself.

Comments included

• Pages designed to accommodate varying device sizes are often broken by the behavior in the viewport meta proposal.
• Many use cases can be solved by using max-width/height on the root element to determine an appropriate viewport size, so UAs should try to use that instead. However, this technique has trouble with fixed positioning.
• Interaction with Media Queries must be defined, perhaps similar to @page { size: ... }
• @viewport has ways of indicating a preferred fixed size, but does not allow a range of valid sizes from which the UA could choose the most appropriate for its device.
• A guiding principle would be to specify only those things that would break web content if a UA decides to do it differently. This avoids overspecifying things that should be within the UA’s jurisdiction.

Resolved: CSS Device Adaptation added to charter at medium priority, Rune to edit along with someone from Apple.

Full Minutes Monday

Minutes and Resolutions 2010-08-18

• Reviewed F2F agenda
• CSS2.1 Beta 3 published
• Resolved: New proposal accepted for CSS2.1 Issue 56.
• Resolved: Proposal accepted for CSS2.1 Issue 137.
• Discussed visibility and text-decoration; discussion moved to F2F.
• Please review new proposal for CSS2.1 Issue 159 for next week.
• Resolved: For CSS2.1 Issue 170, mark min-height/max-height undefined on table rows, cells, etc. in CSS2.1.
• Proposed: Make Appendix G informative. Decision to be made next week. CSS2.1 Issue 186
• Resolved: Accepted proposal for CSS2.1 Issue 187 to make atomic inlines other than replaced elements with display ‘inline’ neutral wrt bidi.
• Resolved: Proposal accepted for CSS2.1 Issue 190.
• In the interest of completing REC, will be setting a stop date for accepting CSS2.1 issues soon.
• CSSWG will consider moving CSS2.1 from LC to PR if possible, instead of going back through CR again.

Full minutes

Minutes and Resolutions 2010-08-11

• CSS2.1 Test Suite Beta 3 scheduled for this weekend; please try to get test fixes in by then.
• Resolved: dbaron’s proposal accepted for CSS2.1 Issue 185 with modifications in the minutes.
• Resolved: Bert’s proposal accepted for CSS2.1 Issue 118 with modifications suggested by Steve Zilles.
• Discussed interaction of text-decoration and visibility (CSS2.1 Issue 144) with no conclusion.

Full minutes

Minutes and Resolutions 2010-08-04

• Resolved: Proposal for CSS2.1 Issue 120 accepted with changes mentioned in minutes.
• Resolved: Proposal accepted for CSS2.1 Issue 167 as corrected by Bert.
• Discussed CSS2.1 Issue 118 and definition of em box.
• Resolved: For CSS2.1 Issue 184, add “Pseudo-elements behave just like real elements except as described below and elsewhere (i.e. section 12.1).” to 5.12.
• Discussed zero-height floats. (CSS2.1 Issue 185) Proposed resolution to not consider them for line-box shortening.

Full minutes

« Newer articles Older articles »

Archives

Search for:

Browse by date:

• March 2026 (1)
• October 2025 (2)
• September 2025 (8)
• August 2025 (3)
• July 2025 (5)
• June 2025 (5)
• May 2025 (6)
• April 2025 (4)
• March 2025 (8)
• February 2025 (6)
• January 2025 (4)
• December 2024 (4)
• November 2024 (8)
• October 2024 (6)
• September 2024 (6)
• August 2024 (9)
• July 2024 (4)
• June 2024 (2)
• May 2024 (7)
• April 2024 (3)
• March 2024 (7)
• February 2024 (4)
• January 2024 (4)
• December 2023 (3)
• November 2023 (5)
• October 2023 (4)
• September 2023 (3)
• August 2023 (5)
• July 2023 (1)
• June 2023 (4)
• May 2023 (5)
• April 2023 (5)
• March 2023 (9)
• February 2023 (4)
• January 2023 (3)
• December 2022 (4)
• November 2022 (3)
• October 2022 (5)
• September 2022 (2)
• August 2022 (3)
• July 2022 (4)
• June 2022 (4)
• May 2022 (5)
• April 2022 (4)
• March 2022 (3)
• February 2022 (3)
• January 2022 (7)
• December 2021 (2)
• November 2021 (4)
• October 2021 (3)
• September 2021 (6)
• August 2021 (6)
• July 2021 (3)
• June 2021 (6)
• May 2021 (6)
• April 2021 (2)
• March 2021 (6)
• February 2021 (3)
• January 2021 (5)
• December 2020 (10)
• November 2020 (5)
• October 2020 (1)
• September 2020 (6)
• August 2020 (7)
• July 2020 (5)
• June 2020 (9)
• May 2020 (6)
• April 2020 (6)
• March 2020 (4)
• February 2020 (2)
• January 2020 (3)
• December 2019 (3)
• November 2019 (5)
• October 2019 (7)
• September 2019 (1)
• August 2019 (5)
• July 2019 (8)
• June 2019 (2)
• May 2019 (5)
• April 2019 (4)
• March 2019 (3)
• February 2019 (2)
• January 2019 (5)
• December 2018 (3)
• November 2018 (6)
• October 2018 (3)
• September 2018 (4)
• August 2018 (12)
• July 2018 (4)
• June 2018 (8)
• May 2018 (9)
• April 2018 (5)
• March 2018 (6)
• February 2018 (2)
• January 2018 (3)
• December 2017 (9)
• November 2017 (2)
• October 2017 (4)
• September 2017 (5)
• August 2017 (7)
• July 2017 (6)
• June 2017 (4)
• May 2017 (3)
• April 2017 (2)
• March 2017 (6)
• February 2017 (16)
• January 2017 (2)
• December 2016 (4)
• November 2016 (5)
• October 2016 (4)
• September 2016 (3)
• August 2016 (4)
• July 2016 (4)
• June 2016 (14)
• May 2016 (6)
• April 2016 (7)
• March 2016 (10)
• February 2016 (1)
• January 2016 (7)
• December 2015 (5)
• November 2015 (3)
• October 2015 (3)
• September 2015 (16)
• August 2015 (3)
• July 2015 (6)
• June 2015 (11)
• May 2015 (7)
• April 2015 (6)
• March 2015 (6)
• February 2015 (2)
• January 2015 (7)
• December 2014 (6)
• November 2014 (3)
• October 2014 (10)
• September 2014 (4)
• August 2014 (2)
• July 2014 (4)
• June 2014 (8)
• May 2014 (5)
• April 2014 (5)
• March 2014 (8)
• February 2014 (14)
• January 2014 (5)
• December 2013 (3)
• November 2013 (6)
• October 2013 (12)
• September 2013 (5)
• August 2013 (5)
• July 2013 (14)
• June 2013 (4)
• May 2013 (8)
• April 2013 (8)
• March 2013 (9)
• February 2013 (6)
• January 2013 (7)
• December 2012 (6)
• November 2012 (9)
• October 2012 (8)
• September 2012 (1)
• August 2012 (17)
• July 2012 (2)
• June 2012 (6)
• May 2012 (11)
• April 2012 (9)
• March 2012 (8)
• February 2012 (7)
• January 2012 (5)
• December 2011 (13)
• November 2011 (1)
• October 2011 (5)
• September 2011 (8)
• August 2011 (17)
• July 2011 (2)
• June 2011 (6)
• May 2011 (7)
• April 2011 (4)
• March 2011 (6)
• February 2011 (6)
• January 2011 (4)
• December 2010 (3)
• November 2010 (8)
• October 2010 (8)
• September 2010 (4)
• August 2010 (3)
• July 2010 (5)
• June 2010 (6)
• May 2010 (4)
• April 2010 (6)
• March 2010 (3)
• February 2010 (5)
• January 2010 (5)
• December 2009 (4)
• November 2009 (2)
• October 2009 (6)
• September 2009 (3)
• August 2009 (3)
• July 2009 (4)
• June 2009 (11)
• March 2009 (9)
• February 2009 (4)
• January 2009 (3)
• November 2008 (8)
• October 2008 (3)
• September 2008 (6)
• August 2008 (1)
• July 2008 (4)
• June 2008 (4)
• May 2008 (4)
• April 2008 (10)
• March 2008 (3)
• February 2008 (3)
• January 2008 (2)
• December 2007 (7)
• November 2007 (8)
• October 2007 (3)
• September 2007 (5)
• August 2007 (3)
• July 2007 (4)
• May 2007 (1)

Browse by category:

• Best Practices (1)
• Feedback (5)
• general (30)
• i18n (2)
• publications (236)
• resolutions (892)
• testing (2)
• Uncategorized (14)

Site navigation

• 
• CSS home
• Learn & use
• Soft­ware
• Par­tic­i­pate / drafts
• 

Contact: Bert Bos
Copyright © 2020 W3C^®

Last updated 2026-03-06 17:10:32.000000