CINXE.COM

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html lang="en" xmlns="http://www.w3.org/1999/xhtml"> <head profile="http://microformats.org/profile/hcard"> <title>CSS WG Blog</title> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta name="viewport" content="width=device-width" /> <link rel="stylesheet" title="Main" media="screen, handheld, projection, tv" href="/Style/CSS/w3c-2010/main" /> <link rel="alternate stylesheet" title="Cascade" media="screen, handheld, projection, tv" href="/Style/CSS/floatspan-n" /> <link rel="alternate stylesheet" title="Cascade" media="screen, handheld, projection, tv" href="/Style/CSS/daily-color" /> <link rel="alternate stylesheet" title="Cascade (older browsers)" media="screen, handheld, projection, tv" href="/Style/CSS/floatspan" /> <link rel="alternate stylesheet" title="Cascade (older browsers)" media="screen, handheld, projection, tv" href="/Style/CSS/daily-color" /> <link rel="alternate stylesheet" title="Asymmetric" media="screen, handheld, projection, tv" href="/Style/CSS/asymmetric" /> <link rel="alternate stylesheet" title="Draft 3" media="screen, projection, tv" href="/Style/CSS/draft" /> <link rel="alternate stylesheet" title="Draft 2" media="screen, projection, tv" href="/Style/CSS/draft-rg" /> <link rel="stylesheet" media="print" href="/Style/CSS/twocolumn-print" /> <link rel="home" title="W3C" href="/" /> <link rel="top" title="CSS" href="/Style/CSS/" /> <link rel="first" title="CSS" href="/Style/CSS/" /> <link rel="last" title="The Future Of CSS (syndicator)" href="/Style/CSS/Planet/" /> <link rel="chapter" title="Roadmap" href="/Style/CSS/current-work" /> <link rel="chapter" title="Examples" href="/Style/Examples/007/" /> <link rel="bookmark" title="Activities" href="/Consortium/activities" /> <link rel="bookmark" title="Tech. reports" href="/TR/" /> <link rel="bookmark" title="Translations" href="/Consortium/Translation/" /> <link rel="bookmark" title="Software" href="/Status" /> <link rel="index" title="Site index" href="/Consortium/siteindex" /> <link rel="search" title="Search" href="https://search.w3.org/" /> <link rel="copyright" title="Copyright" href="/Consortium/Legal/ipr-notice.html#Copyright" /> <link rev="made" href="mailto:bert@w3.org%20(Bert%20Bos)" /> <link rel="author" href="mailto:bert@w3.org%20(Bert%20Bos)" /> <link rel="pingback" href="https://www.w3.org/blog/CSS/xmlrpc.php" /> <link rel="alternate" type="application/atom+xml" title="Atom" href="https://www.w3.org/blog/CSS/feed/atom/" /> <style type="text/css" title="Main"> div.metadata {font-size: smaller; margin-bottom: 0.6em} #archives ul {columns: 10em} #archives {color: #333; background: #C1D2E7; border-radius: .5em; overflow: auto} #archives > *:first-child {margin-top: 0} </style> </head> <body> <h1><em>CSS WG Blog</em> front page</h1> <div class="section" id="intro"> <p>This is a page from the <a href="https://www.w3.org/blog/CSS" ><strong>Cascading Style Sheets Working Group Blog.</strong></a> Some other places to find information are the <a href="/Style/CSS/current-work">“current work” page,</a> the <a href="http://lists.w3.org/Archives/Public/www-style/" >www-style mailing list,</a> the <a href="/Style/CSS/Planet/" >Future of CSS</a> syndicator, and the <a href='https://github.com/w3c/csswg-drafts/issues'>issue list</a> on Github.</p> <p>Do you want to know how the <a href="/Style/CSS/members" >CSS WG</a> works? <a href="http://fantasai.inkedblade.net/contact">Fantasai</a> has written <a href="http://fantasai.inkedblade.net/weblog/2011/inside-csswg/" ><cite>about:csswg, An Inside View of the CSS Working Group at W3C.</cite></a></p> </div> <div class="section" id="post-4542"> <h2>Minutes Telecon 2025-02-19</h2> <div class="metadata"> <p>By <em class="author">Dael Jackson</em> <span class="updated">February 20, 2025</span> (<a href="https://www.w3.org/blog/CSS/2025/02/20/minutes-2025-02-19/">Permalink</a>)<br /> <span class="categories">Categories: <strong><a title="Browse category" href="https://www.w3.org/blog/CSS/category/resolutions/">resolutions</a> </strong></span></p> </div> <ul> <li><b>Resolved: </b>Publish <a href="https://drafts.csswg.org/css-2024/">Snapshot 2024</a> from the current draft, as a Group Note (<a href="https://github.com/w3c/csswg-drafts/issues/11696">Issue #11696</a>: Finish up CSS Snapshot 2024)</li> <li><b>Resolved: </b>block-step-size inherits, and does not activate step sizing (<a href="https://github.com/w3c/csswg-drafts/issues/1902">Issue #1902</a>: Inherit block-step-size)</li> <li><b>Resolved: </b>Add a new “none” initial value to block-step-align; all other values turn on step sizing (<a href="https://github.com/w3c/csswg-drafts/issues/1902">Issue #1902</a>)</li> <li><b>Resolved: </b>Try option 2 [use the scrollIntoView() position of the non-skipped ancestor of the marker for determining when the marker is active] (<a href="https://github.com/w3c/csswg-drafts/issues/11705">Issue #11705</a>: Should ::scroll-marker pseudo-elements within skipped content-visibility: auto elements be discovered?)</li> <li><b>Resolved: </b>Specify this new parsing behavior for all substitution functions, and some sort of spread-like thing (<a href="https://github.com/w3c/csswg-drafts/issues/11500">Issue #11500</a>: Short-circuit if() evaluation)</li> <li>There wasn’t time to discuss all the questions in <a href="https://github.com/w3c/csswg-drafts/issues/11208">issue #11208</a> (reading-flow and mix of auto-flow and explicit items). The group leaned toward having the ability to set a property which says reading-flow:`stick-with-source-order` to answer the first question.</li> </ul> <p><a href="https://lists.w3.org/Archives/Public/www-style/2025Feb/0014.html">Full Meeting Minutes</a></p> </div> <div class="section" id="post-4539"> <h2>Minutes Sizing Breakout 2025-02-19</h2> <div class="metadata"> <p>By <em class="author">Dael Jackson</em> <span class="updated">February 20, 2025</span> (<a href="https://www.w3.org/blog/CSS/2025/02/20/minutes-sizing-breakout-2025-02-19/">Permalink</a>)<br /> <span class="categories">Categories: <strong><a title="Browse category" href="https://www.w3.org/blog/CSS/category/resolutions/">resolutions</a> </strong></span></p> </div> <h3>CSS Sizing Breakout</h3> <ul> <li><b>Resolved: </b>Fixed table layout is triggered except when inline-size is auto (<a href="https://github.com/w3c/csswg-drafts/issues/10937">Issue #10937</a>: What sizing keywords allow fixed table mode?)</li> <li><b>Resolved: </b>Accept proposal (<a href="https://github.com/w3c/csswg-drafts/issues/11044">Issue #11044</a>: How does height: stretch interact with margin collapsing with parent)</li> <li><b>Resolved: </b>See if implementations can match the spec and revisit issue later (<a href="https://github.com/w3c/csswg-drafts/issues/11452">Issue #11452</a>: Nobody follows the spec about cyclic percentages in preferred&max sizing properties of replaced element)</li> <li><b>Resolved: </b>min-size: stretch behaves as zero, max-size; stretch as infinity, when in an indefinite container (<a href="https://github.com/w3c/csswg-drafts/issues/11006">Issue #11006</a>: Does indefinite `stretch` behave as automatic size or as initial value?)</li> </ul> <p><a href="https://lists.w3.org/Archives/Public/www-style/2025Feb/0012.html">Full Meeting Minutes</a></p> </div> <div class="section" id="post-4537"> <h2>Minutes Color HDR Breakout 2025-02-12</h2> <div class="metadata"> <p>By <em class="author">Dael Jackson</em> <span class="updated">February 14, 2025</span> (<a href="https://www.w3.org/blog/CSS/2025/02/14/minutes-breakout-2025-02-12/">Permalink</a>)<br /> <span class="categories">Categories: <strong><a title="Browse category" href="https://www.w3.org/blog/CSS/category/resolutions/">resolutions</a> </strong></span></p> </div> <ul> <li><b>Resolved: </b>Add current proposal as a note into the spec (<a href="https://github.com/w3c/csswg-drafts/issues/11616">Issue #11616</a>: CSS syntax for HDR colors parameterized by headroom)</li> <li><b>Resolved:</b>Change high to no-limit (<a href="https://github.com/w3c/csswg-drafts/issues/11698">Issue #11698</a>: New values for dynamic-range-limit property)</li> <li>weinig will create a PR to clarify the language called out in <a href="https://github.com/w3c/csswg-drafts/issues/11672">issue #11672</a> (Clarification on the grammar / spec text for `dynamic-range-limit-mix()`)</li> </ul> <p><a href="https://lists.w3.org/Archives/Public/www-style/2025Feb/0008.html">Full Meeting Minutes</a></p> </div> <div class="section" id="post-4534"> <h2>Minutes Telecon 2025-02-12</h2> <div class="metadata"> <p>By <em class="author">Dael Jackson</em> <span class="updated">February 13, 2025</span> (<a href="https://www.w3.org/blog/CSS/2025/02/13/minutes-2025-02-12/">Permalink</a>)<br /> <span class="categories">Categories: <strong><a title="Browse category" href="https://www.w3.org/blog/CSS/category/resolutions/">resolutions</a> </strong></span></p> </div> <ul> <li><b>Resolved: </b>We use a caret approach. It’s part of the syntax and not part of the name. Weak/strong with the same name is ok (<a href="https://github.com/w3c/csswg-drafts/issues/6323">Issue #6323</a>: Allow authors to explicitly place unlayered styles in the cascade layer order)</li> <li><b>Resolved: </b>Strength is exposed in CSSOM, details tbd (<a href="https://github.com/w3c/csswg-drafts/issues/6323">Issue #6323</a>)</li> <li>Solving <a href="https://github.com/w3c/csswg-drafts/issues/3720">issue #3720</a> (Add a ‘hairline’ border-width value) was supported by the team, but the proposal needed more details added.</li> <li><b>Resolved: </b>shape() remains as-is, spec subset that is more tightly tied to SVG <code>path</code> for a path() overload (<a href="https://github.com/w3c/csswg-drafts/issues/10647">Issue #10647</a>: Overload `path()` for CSS-y SVG path syntax instead of taking up `shape()`)</li> <li>There wasn’t clear support for the proposal to address <a href="https://github.com/w3c/csswg-drafts/issues/10773">issue #10773</a> (Elements with content-visibility in new Document) by having the content-visibility:auto determination run again when there is an incoming viewport. Discussion to clarify the proposal and discuss alternatives will continue on the issue.</li> </ul> <p><a href="https://lists.w3.org/Archives/Public/www-style/2025Feb/0007.html">Full Meeting Minutes</a></p> </div> <div class="section" id="post-4531"> <h2>Minutes Telecon 2025-01-22</h2> <div class="metadata"> <p>By <em class="author">Dael Jackson</em> <span class="updated">January 24, 2025</span> (<a href="https://www.w3.org/blog/CSS/2025/01/24/minutes-2025-01-22/">Permalink</a>)<br /> <span class="categories">Categories: <strong><a title="Browse category" href="https://www.w3.org/blog/CSS/category/resolutions/">resolutions</a> </strong></span></p> </div> <ul> <li><b>Resolved: </b>Adopt safe-area-max-inset-* values (<a href="https://github.com/w3c/csswg-drafts/issues/11019">Issue #11019</a>: Maximum safe area inset values to allow sliding bottom bar)</li> <li><b>Resolved: </b>enum ScrollIntoViewContainer { “all”, “nearest” }, defaulting to `all`, expanding to element in the future if needed (<a href="https://github.com/w3c/csswg-drafts/issues/9452">Issue #9452</a>: Option for scrollIntoView that doesn’t propagate to ancestors)</li> <li><b>Resolved: </b>UAs MUST preserve user privacy (<a href="https://github.com/w3c/csswg-drafts/issues/11151">Issue #11151</a>: Proposal: Update :visited language to state UAs must preserve user privacy)</li> <li>There wasn’t a strong preference between the two options for <a href="https://github.com/w3c/csswg-drafts/issues/9724">issue #9724</a> (What does the `white-space-collapse` apply to when white-space trimming/positioning) will be written up in advance of the F2F. This will allow the authors to gain feedback on ease of implementation before selecting one option.</li> <li><b>Resolved: </b>Close no change (<a href="https://github.com/w3c/csswg-drafts/issues/10831">Issue #10831</a>: `anchor()` Fallback type inconsistency vs WPT)</li> <li>The spring F2F will be April 15 to 17. There is a poll for dates for the summer F2F. Group members are asked to fill in their availability.</li> </ul> <p><a href="https://lists.w3.org/Archives/Public/www-style/2025Jan/0016.html">Full Meeting Minutes</a></p> </div> <div class="section" id="post-4529"> <h2>Minutes Overflow Breakout 2025-01-22</h2> <div class="metadata"> <p>By <em class="author">Dael Jackson</em> <span class="updated">January 23, 2025</span> (<a href="https://www.w3.org/blog/CSS/2025/01/23/minutes-overflow-breakout-2025-01-22/">Permalink</a>)<br /> <span class="categories">Categories: <strong><a title="Browse category" href="https://www.w3.org/blog/CSS/category/resolutions/">resolutions</a> </strong></span></p> </div> <h3><a href="https://drafts.csswg.org/css-overflow-4/">CSS Overflow</a> Breakout</h3> <ul> <li><b>Resolved: </b>Spec scroll-marker-contain (<a href="https://github.com/w3c/csswg-drafts/issues/10916">Issue #10916</a>: Creating scroll-marker groups within which to select an active marker)</li> <li><b>Resolved: </b>Adopt everything in the <a href="https://github.com/w3c/csswg-drafts/issues/11098#issuecomment-2447214498">Oct 30 comment</a> (<a href="https://github.com/w3c/csswg-drafts/issues/11098">Issue #11098</a>: What is the active :checked marker when some markers point to elements within different scrolling containers?)</li> <li><b>Resolved: </b>Only propagate the scroll into view for a scroll marker up to the common ancestor scroller of the targets (<a href="https://github.com/w3c/csswg-drafts/issues/11138">Issue #11138</a>: Limit scrolling to the associated scroll container when activating a marker)</li> <li><b>Resolved: </b>For a 2D scroller, we will define an algorithm that uses a primary direction that defaults to the block axis (<a href="https://github.com/w3c/csswg-drafts/issues/11198">Issue #11198</a>: Active marker in 2d scroller?)</li> <li><b>Resolved: </b>::scroll-marker-group applies containment when it is in-flow only (<a href="https://github.com/w3c/csswg-drafts/issues/11166">Issue #11166</a>: Can we relax size containment on ::scroll-marker-group?)</li> <li><b>Resolved: </b>The document.activeElement is the scroll container for a focused ::scroll-marker or ::scroll-button. :focus matches only on the specific focused pseudo-element. :focus-within matches on the ::scroll-marker-group for ::scroll-marker, and the scroll container and all ancestors for both ::scroll-marker and ::scroll-button (<a href="https://github.com/w3c/csswg-drafts/issues/11361">Issue #11361</a>: :focus and :focus-within styles with focused scroller pseudo-element)</li> <li>There were some concerns expressed that the proposal for <a href="https://github.com/w3c/csswg-drafts/issues/10868">issue #10868</a> (What counts as “immediately preceding” for `block-ellipsis`?) would create inconsistent definitions, however time ran out before the group could discuss further.</li> </ul> <p><a href="https://lists.w3.org/Archives/Public/www-style/2025Jan/0015.html">Full Meeting Minutes</a></p> </div> <div class="section" id="post-4526"> <h2>Minutes Telecon 2025-01-15</h2> <div class="metadata"> <p>By <em class="author">Dael Jackson</em> <span class="updated">January 16, 2025</span> (<a href="https://www.w3.org/blog/CSS/2025/01/16/minutes-2025-01-15/">Permalink</a>)<br /> <span class="categories">Categories: <strong><a title="Browse category" href="https://www.w3.org/blog/CSS/category/resolutions/">resolutions</a> </strong></span></p> </div> <ul> <li><b>Resolved: </b>:has-slotted should use the flattened tree to resolve if content is slotted or not. We could later discuss a different pseudo-class for the other behavior (<a href="https://github.com/w3c/csswg-drafts/issues/6867">Issue #6867</a>: Pseudo-class to indicate when a slot has content)</li> <li><b>Resolved: </b>Do NOT establish BFC for block-step-size with details on when the extra space gets added to the bottom only to be determined in future conversations (<a href="https://github.com/w3c/csswg-drafts/issues/11325">Issue #11325</a>: `block-step-size` should not establish an independent formatting context)</li> <li><b>Resolved: </b>Close no change (<a href="https://github.com/w3c/csswg-drafts/issues/1902">Issue #1902</a>: Inherit block-step-size)</li> <li>ChrisL has already responded to some comments on the rechartering request (<a href="https://github.com/w3c/csswg-drafts/issues/10671">Issue #10671</a>) and astearns will reply to the remaining one. ChrisL will draft up a proposal to address the concerns in Brave’s objection and have it for the working group to review shortly.</li> </ul> <p><a href="https://lists.w3.org/Archives/Public/www-style/2025Jan/0010.html">Full Meeting Minutes</a></p> </div> <div class="section" id="post-4523"> <h2>Minutes Telecon 2025-01-08</h2> <div class="metadata"> <p>By <em class="author">Dael Jackson</em> <span class="updated">January 9, 2025</span> (<a href="https://www.w3.org/blog/CSS/2025/01/09/minutes-2025-01-08/">Permalink</a>)<br /> <span class="categories">Categories: <strong><a title="Browse category" href="https://www.w3.org/blog/CSS/category/resolutions/">resolutions</a> </strong></span></p> </div> <ul> <li><b>Resolved: </b>text-box-trim does not change height contribution of inline (<a href="https://github.com/w3c/csswg-drafts/issues/10834">Issue #10834</a>: inline boxes and line-fit-edge vs text-box-trim/edge)</li> <li>fantasai will make a testcase for the above resolution and report back on WebKit/Chrome implementation status.</li> <li><b>Resolved: </b>If text-box-trim reduces the effective height of the inline box compared to line-fit-edge, that amount is propagated as a negative margin (the same way as a specified negative margin is propagated) to inline descendants (<a href="https://github.com/w3c/csswg-drafts/issues/10834">Issue #10384</a>)</li> <li><b>Resolved: </b>Apply text-box-trim to a column box or spanner iff it is adjacent to the relevant edge (<a href="https://github.com/w3c/csswg-drafts/issues/11363">Issue #11363</a>: text-box-trim and multi-column containers)</li> <li>There was discussion around the naming decision for <a href="https://github.com/w3c/csswg-drafts/issues/10975">issue #10975</a> (:local-link should have a more precise name) but no clear answer was discovered during the call. Discussion will continue on the issue to outline possibilities.</li> <li><b>Resolved: </b>`:has-slotted` should match when the fallback content is not being displayed (<a href="https://github.com/w3c/csswg-drafts/issues/6867">Issue #6867</a>: Pseudo-class to indicate when a slot has content)</li> <li><b>Resolved: </b>Restrict ordering such that `to` or `by` would need to come first (<a href="https://github.com/w3c/csswg-drafts/issues/10666">Issue #10666</a>: Order of points and control points in `shape()`)</li> </ul> <p><a href="https://lists.w3.org/Archives/Public/www-style/2025Jan/0006.html">Full Meeting Minutes</a></p> </div> <div class="section" id="post-4519"> <h2>Minutes Telecon 2024-12-18</h2> <div class="metadata"> <p>By <em class="author">Dael Jackson</em> <span class="updated">December 20, 2024</span> (<a href="https://www.w3.org/blog/CSS/2024/12/20/minutes-telecon-2024-12-18/">Permalink</a>)<br /> <span class="categories">Categories: <strong><a title="Browse category" href="https://www.w3.org/blog/CSS/category/resolutions/">resolutions</a> </strong></span></p> </div> <ul> <li>There were multiple clarifying questions about the proposal in <a href="https://github.com/w3c/csswg-drafts/issues/11185">issue #11185</a> (select:hover and select:active styles). <ul> <li>There is an exception for top layer in the proposal, but it wasn’t clear if that exception was enough to prevent breakage in menus. The carousel scroll-marker/group is not in the top layer and would still need some exception as well.</li> <li>Creating a CSS property was discussed as an alternative, though it could create loops so needed to be approached mindfully.</li> <li>Discussion will continue on the github issue.</li> </ul> </li> <li><b>Resolved: </b>Adopt ident() function into css-values-5 (<a href="https://github.com/w3c/csswg-drafts/issues/9141">Issue #9141</a>: A way to dynamically construct custom-ident and dashed-ident values)</li> <li><b>Resolved: </b>Use the `match-element` keyword for this and disallow it as a value in view-transitions-1 spec (<a href="https://github.com/w3c/csswg-drafts/issues/10995">Issue #10995</a>: Allow an auto-generated `view-transition-name` that doesn’t default to ID)</li> <li>The proposal for <a href="https://github.com/w3c/csswg-drafts/issues/10834">issue #10834</a> (inline boxes and line-fit-edge vs text-box-trim/edge) was introduced for more discussion in the next meeting.</li> <li>Group members were requested to <a href="https://wiki.csswg.org/planning/cupertino-2025">register</a> for the next F2F if they’re planning on going.</li> </ul> <p><a href="https://lists.w3.org/Archives/Public/www-style/2024Dec/0012.html">Full Meeting Minutes</a></p> </div> <div class="section" id="post-4516"> <h2>Minutes Telecon 2024-12-11</h2> <div class="metadata"> <p>By <em class="author">Dael Jackson</em> <span class="updated">December 12, 2024</span> (<a href="https://www.w3.org/blog/CSS/2024/12/12/minutes-2024-12-11/">Permalink</a>)<br /> <span class="categories">Categories: <strong><a title="Browse category" href="https://www.w3.org/blog/CSS/category/resolutions/">resolutions</a> </strong></span></p> </div> <ul> <li><b>Resolved</b>: WG likes the logo and would like to officially endorse it, will investigate what that means (<a href="https://github.com/w3c/csswg-drafts/issues/11193">Issue #11193</a>: Adoption of the logo created by the CSS Next CG)</li> <li><b>Resolved: </b>FPWD of <a href="https://drafts.csswg.org/css-color-hdr-1/">color hdr</a> (<a href="https://github.com/w3c/csswg-drafts/issues/11344">Issue #11344</a>: Time for FPWD)</li> <li><b>Resolved: </b>FPWD of <a href="https://drafts.csswg.org/css-display-4/">Display 4</a></li> <li><b>Resolved: </b>FPWD of <a href="https://drafts.csswg.org/css-overflow-5/">Overflow 5</a></li> <li><b>Resolved: </b>FPWD of <a href="https://drafts.csswg.org/css-multicol-2/">Multicol 2</a> (as a full spec, not diff)</li> <li><b>Resolved: </b>scrollsnapchanging uses the targeted location for targeted scrolls, but does not predict the destination of momentum scrolling (uses the current scroll location instead) (<a href="https://github.com/w3c/csswg-drafts/issues/10838">Issue #10838</a>: Should scrollsnapchanging target the currently visible element during flings)</li> <li><b>Resolved: </b>`scroll-initial-target: none | nearest` (<a href="https://github.com/w3c/csswg-drafts/issues/11173">Issue #11173</a>: scroll-start-target: auto doesn’t match general meaning of auto)</li> <li><b>Resolved: </b>`overflow-clip-margin: content-box` applies to scrollable boxes (<a href="https://github.com/w3c/csswg-drafts/issues/10745">Issue #10745</a>: Should overflow-clip-margin apply to scrollable boxes?)</li> <li>There was interest in addressing the use case in <a href="https://github.com/w3c/csswg-drafts/issues/10674">issue #10674</a> (UAs inconsistent in how OS font settings affect the default font-size `medium`) but the group ran out of time before they could reach agreement on the best approach. Discussion will continue on github.</li> </ul> <p><a href="https://lists.w3.org/Archives/Public/www-style/2024Dec/0006.html">Full Meeting Minutes</a></p> </div> <div class="section"> <p class="more"><a href="https://www.w3.org/blog/CSS/page/2/" > Older articles »</a></p> </div> <div class="section" id="archives"> <h2>Archives</h2> <p class="feed"><a href="https://www.w3.org/blog/CSS/feed/atom/"><img alt="(Also available as Atom news feed.)" src="/Style/CSS/w3c-2010/feed" title="News feed" /></a></p> <form action="https://www.w3.org/blog/CSS/"> <p><label for="s">Search for:</label> <input value="" name="s" id="s" /> <input type="submit" value="Submit" /></p> </form> <p>Browse by date:</p> <ul> <li><a href='https://www.w3.org/blog/CSS/2025/02/'>February 2025</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2025/01/'>January 2025</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2024/12/'>December 2024</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2024/11/'>November 2024</a> (8)</li> <li><a href='https://www.w3.org/blog/CSS/2024/10/'>October 2024</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2024/09/'>September 2024</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2024/08/'>August 2024</a> (9)</li> <li><a href='https://www.w3.org/blog/CSS/2024/07/'>July 2024</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2024/06/'>June 2024</a> (2)</li> <li><a href='https://www.w3.org/blog/CSS/2024/05/'>May 2024</a> (7)</li> <li><a href='https://www.w3.org/blog/CSS/2024/04/'>April 2024</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2024/03/'>March 2024</a> (7)</li> <li><a href='https://www.w3.org/blog/CSS/2024/02/'>February 2024</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2024/01/'>January 2024</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2023/12/'>December 2023</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2023/11/'>November 2023</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2023/10/'>October 2023</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2023/09/'>September 2023</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2023/08/'>August 2023</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2023/07/'>July 2023</a> (1)</li> <li><a href='https://www.w3.org/blog/CSS/2023/06/'>June 2023</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2023/05/'>May 2023</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2023/04/'>April 2023</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2023/03/'>March 2023</a> (9)</li> <li><a href='https://www.w3.org/blog/CSS/2023/02/'>February 2023</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2023/01/'>January 2023</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2022/12/'>December 2022</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2022/11/'>November 2022</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2022/10/'>October 2022</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2022/09/'>September 2022</a> (2)</li> <li><a href='https://www.w3.org/blog/CSS/2022/08/'>August 2022</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2022/07/'>July 2022</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2022/06/'>June 2022</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2022/05/'>May 2022</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2022/04/'>April 2022</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2022/03/'>March 2022</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2022/02/'>February 2022</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2022/01/'>January 2022</a> (7)</li> <li><a href='https://www.w3.org/blog/CSS/2021/12/'>December 2021</a> (2)</li> <li><a href='https://www.w3.org/blog/CSS/2021/11/'>November 2021</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2021/10/'>October 2021</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2021/09/'>September 2021</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2021/08/'>August 2021</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2021/07/'>July 2021</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2021/06/'>June 2021</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2021/05/'>May 2021</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2021/04/'>April 2021</a> (2)</li> <li><a href='https://www.w3.org/blog/CSS/2021/03/'>March 2021</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2021/02/'>February 2021</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2021/01/'>January 2021</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2020/12/'>December 2020</a> (10)</li> <li><a href='https://www.w3.org/blog/CSS/2020/11/'>November 2020</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2020/10/'>October 2020</a> (1)</li> <li><a href='https://www.w3.org/blog/CSS/2020/09/'>September 2020</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2020/08/'>August 2020</a> (7)</li> <li><a href='https://www.w3.org/blog/CSS/2020/07/'>July 2020</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2020/06/'>June 2020</a> (9)</li> <li><a href='https://www.w3.org/blog/CSS/2020/05/'>May 2020</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2020/04/'>April 2020</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2020/03/'>March 2020</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2020/02/'>February 2020</a> (2)</li> <li><a href='https://www.w3.org/blog/CSS/2020/01/'>January 2020</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2019/12/'>December 2019</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2019/11/'>November 2019</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2019/10/'>October 2019</a> (7)</li> <li><a href='https://www.w3.org/blog/CSS/2019/09/'>September 2019</a> (1)</li> <li><a href='https://www.w3.org/blog/CSS/2019/08/'>August 2019</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2019/07/'>July 2019</a> (8)</li> <li><a href='https://www.w3.org/blog/CSS/2019/06/'>June 2019</a> (2)</li> <li><a href='https://www.w3.org/blog/CSS/2019/05/'>May 2019</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2019/04/'>April 2019</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2019/03/'>March 2019</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2019/02/'>February 2019</a> (2)</li> <li><a href='https://www.w3.org/blog/CSS/2019/01/'>January 2019</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2018/12/'>December 2018</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2018/11/'>November 2018</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2018/10/'>October 2018</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2018/09/'>September 2018</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2018/08/'>August 2018</a> (12)</li> <li><a href='https://www.w3.org/blog/CSS/2018/07/'>July 2018</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2018/06/'>June 2018</a> (8)</li> <li><a href='https://www.w3.org/blog/CSS/2018/05/'>May 2018</a> (9)</li> <li><a href='https://www.w3.org/blog/CSS/2018/04/'>April 2018</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2018/03/'>March 2018</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2018/02/'>February 2018</a> (2)</li> <li><a href='https://www.w3.org/blog/CSS/2018/01/'>January 2018</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2017/12/'>December 2017</a> (9)</li> <li><a href='https://www.w3.org/blog/CSS/2017/11/'>November 2017</a> (2)</li> <li><a href='https://www.w3.org/blog/CSS/2017/10/'>October 2017</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2017/09/'>September 2017</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2017/08/'>August 2017</a> (7)</li> <li><a href='https://www.w3.org/blog/CSS/2017/07/'>July 2017</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2017/06/'>June 2017</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2017/05/'>May 2017</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2017/04/'>April 2017</a> (2)</li> <li><a href='https://www.w3.org/blog/CSS/2017/03/'>March 2017</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2017/02/'>February 2017</a> (16)</li> <li><a href='https://www.w3.org/blog/CSS/2017/01/'>January 2017</a> (2)</li> <li><a href='https://www.w3.org/blog/CSS/2016/12/'>December 2016</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2016/11/'>November 2016</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2016/10/'>October 2016</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2016/09/'>September 2016</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2016/08/'>August 2016</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2016/07/'>July 2016</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2016/06/'>June 2016</a> (14)</li> <li><a href='https://www.w3.org/blog/CSS/2016/05/'>May 2016</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2016/04/'>April 2016</a> (7)</li> <li><a href='https://www.w3.org/blog/CSS/2016/03/'>March 2016</a> (10)</li> <li><a href='https://www.w3.org/blog/CSS/2016/02/'>February 2016</a> (1)</li> <li><a href='https://www.w3.org/blog/CSS/2016/01/'>January 2016</a> (7)</li> <li><a href='https://www.w3.org/blog/CSS/2015/12/'>December 2015</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2015/11/'>November 2015</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2015/10/'>October 2015</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2015/09/'>September 2015</a> (16)</li> <li><a href='https://www.w3.org/blog/CSS/2015/08/'>August 2015</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2015/07/'>July 2015</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2015/06/'>June 2015</a> (11)</li> <li><a href='https://www.w3.org/blog/CSS/2015/05/'>May 2015</a> (7)</li> <li><a href='https://www.w3.org/blog/CSS/2015/04/'>April 2015</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2015/03/'>March 2015</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2015/02/'>February 2015</a> (2)</li> <li><a href='https://www.w3.org/blog/CSS/2015/01/'>January 2015</a> (7)</li> <li><a href='https://www.w3.org/blog/CSS/2014/12/'>December 2014</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2014/11/'>November 2014</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2014/10/'>October 2014</a> (10)</li> <li><a href='https://www.w3.org/blog/CSS/2014/09/'>September 2014</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2014/08/'>August 2014</a> (2)</li> <li><a href='https://www.w3.org/blog/CSS/2014/07/'>July 2014</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2014/06/'>June 2014</a> (8)</li> <li><a href='https://www.w3.org/blog/CSS/2014/05/'>May 2014</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2014/04/'>April 2014</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2014/03/'>March 2014</a> (8)</li> <li><a href='https://www.w3.org/blog/CSS/2014/02/'>February 2014</a> (14)</li> <li><a href='https://www.w3.org/blog/CSS/2014/01/'>January 2014</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2013/12/'>December 2013</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2013/11/'>November 2013</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2013/10/'>October 2013</a> (12)</li> <li><a href='https://www.w3.org/blog/CSS/2013/09/'>September 2013</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2013/08/'>August 2013</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2013/07/'>July 2013</a> (14)</li> <li><a href='https://www.w3.org/blog/CSS/2013/06/'>June 2013</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2013/05/'>May 2013</a> (8)</li> <li><a href='https://www.w3.org/blog/CSS/2013/04/'>April 2013</a> (8)</li> <li><a href='https://www.w3.org/blog/CSS/2013/03/'>March 2013</a> (9)</li> <li><a href='https://www.w3.org/blog/CSS/2013/02/'>February 2013</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2013/01/'>January 2013</a> (7)</li> <li><a href='https://www.w3.org/blog/CSS/2012/12/'>December 2012</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2012/11/'>November 2012</a> (9)</li> <li><a href='https://www.w3.org/blog/CSS/2012/10/'>October 2012</a> (8)</li> <li><a href='https://www.w3.org/blog/CSS/2012/09/'>September 2012</a> (1)</li> <li><a href='https://www.w3.org/blog/CSS/2012/08/'>August 2012</a> (17)</li> <li><a href='https://www.w3.org/blog/CSS/2012/07/'>July 2012</a> (2)</li> <li><a href='https://www.w3.org/blog/CSS/2012/06/'>June 2012</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2012/05/'>May 2012</a> (11)</li> <li><a href='https://www.w3.org/blog/CSS/2012/04/'>April 2012</a> (9)</li> <li><a href='https://www.w3.org/blog/CSS/2012/03/'>March 2012</a> (8)</li> <li><a href='https://www.w3.org/blog/CSS/2012/02/'>February 2012</a> (7)</li> <li><a href='https://www.w3.org/blog/CSS/2012/01/'>January 2012</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2011/12/'>December 2011</a> (13)</li> <li><a href='https://www.w3.org/blog/CSS/2011/11/'>November 2011</a> (1)</li> <li><a href='https://www.w3.org/blog/CSS/2011/10/'>October 2011</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2011/09/'>September 2011</a> (8)</li> <li><a href='https://www.w3.org/blog/CSS/2011/08/'>August 2011</a> (17)</li> <li><a href='https://www.w3.org/blog/CSS/2011/07/'>July 2011</a> (2)</li> <li><a href='https://www.w3.org/blog/CSS/2011/06/'>June 2011</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2011/05/'>May 2011</a> (7)</li> <li><a href='https://www.w3.org/blog/CSS/2011/04/'>April 2011</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2011/03/'>March 2011</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2011/02/'>February 2011</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2011/01/'>January 2011</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2010/12/'>December 2010</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2010/11/'>November 2010</a> (8)</li> <li><a href='https://www.w3.org/blog/CSS/2010/10/'>October 2010</a> (8)</li> <li><a href='https://www.w3.org/blog/CSS/2010/09/'>September 2010</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2010/08/'>August 2010</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2010/07/'>July 2010</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2010/06/'>June 2010</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2010/05/'>May 2010</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2010/04/'>April 2010</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2010/03/'>March 2010</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2010/02/'>February 2010</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2010/01/'>January 2010</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2009/12/'>December 2009</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2009/11/'>November 2009</a> (2)</li> <li><a href='https://www.w3.org/blog/CSS/2009/10/'>October 2009</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2009/09/'>September 2009</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2009/08/'>August 2009</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2009/07/'>July 2009</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2009/06/'>June 2009</a> (11)</li> <li><a href='https://www.w3.org/blog/CSS/2009/03/'>March 2009</a> (9)</li> <li><a href='https://www.w3.org/blog/CSS/2009/02/'>February 2009</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2009/01/'>January 2009</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2008/11/'>November 2008</a> (8)</li> <li><a href='https://www.w3.org/blog/CSS/2008/10/'>October 2008</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2008/09/'>September 2008</a> (6)</li> <li><a href='https://www.w3.org/blog/CSS/2008/08/'>August 2008</a> (1)</li> <li><a href='https://www.w3.org/blog/CSS/2008/07/'>July 2008</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2008/06/'>June 2008</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2008/05/'>May 2008</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2008/04/'>April 2008</a> (10)</li> <li><a href='https://www.w3.org/blog/CSS/2008/03/'>March 2008</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2008/02/'>February 2008</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2008/01/'>January 2008</a> (2)</li> <li><a href='https://www.w3.org/blog/CSS/2007/12/'>December 2007</a> (7)</li> <li><a href='https://www.w3.org/blog/CSS/2007/11/'>November 2007</a> (8)</li> <li><a href='https://www.w3.org/blog/CSS/2007/10/'>October 2007</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2007/09/'>September 2007</a> (5)</li> <li><a href='https://www.w3.org/blog/CSS/2007/08/'>August 2007</a> (3)</li> <li><a href='https://www.w3.org/blog/CSS/2007/07/'>July 2007</a> (4)</li> <li><a href='https://www.w3.org/blog/CSS/2007/05/'>May 2007</a> (1)</li> </ul> <p>Browse by category:</p> <ul> <li><a href="https://www.w3.org/blog/CSS/category/best-practices/"> Best Practices</a> (1)</li> <li><a href="https://www.w3.org/blog/CSS/category/feedback/"> Feedback</a> (4)</li> <li><a href="https://www.w3.org/blog/CSS/category/general/"> general</a> (30)</li> <li><a href="https://www.w3.org/blog/CSS/category/i18n/"> i18n</a> (2)</li> <li><a href="https://www.w3.org/blog/CSS/category/publications/"> publications</a> (232)</li> <li><a href="https://www.w3.org/blog/CSS/category/resolutions/"> resolutions</a> (853)</li> <li><a href="https://www.w3.org/blog/CSS/category/testing/"> testing</a> (2)</li> <li><a href="https://www.w3.org/blog/CSS/category/uncategorized/"> Uncategorized</a> (13)</li> </ul> </div> <div id="banner" class="section"> <h2>Site navigation</h2> <form action="/Help/search"> <ul> <li class="home"><a href="https://www.w3.org/" rel="home"><img alt="W3C" src="https://www.w3.org/Icons/w3c_home" /></a></li> <li><a href="/Style/CSS/" rel="bookmark" title="CSS home page">CSS home</a></li> <li><a href="/Style/CSS/learning" rel="bookmark">Learn & use</a></li> <li><a href="/Style/CSS/software" rel="bookmark">Software</a></li> <li><a href="/Style/CSS/current-work" rel="bookmark" title="Participate in the development of the CSS standard" >Participate / <span title="All specifications and drafts">drafts</span></a></li> <li class="search"><input accesskey="E" id="inputField" maxlength="255" name="q" size="10" /><button accesskey="G" type="submit" name="sa"><img src="/2008/site/images/search-button" alt="Search" title="Search" /></button></li> </ul> </form> </div> <div class="section" id="endmatter"> <address class="vcard"><img alt="[Photo: group photo of the CSS working group in San Francisco]" class="photo" src="/Style/CSS/csswg-2016.jpg" /> Contact: <a class="fn url" href="/People/Bos/">Bert Bos</a><br /> <small><a rel="Copyright" href="/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2020 <a href="/"><acronym title="World Wide Web Consortium" >W3C</acronym><sup>®</sup></a></small></address> <p>Last updated 2025-02-20 23:40:49.000000</p> </div> </body> </html>