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.
@pagecontext, so discussion will continue on the mailing list.
bodyor if it has to come from root or if there are other approaches entirely.
writing-mode: vertical-lron the
rtbased on parent’s ‘display’ & ‘ruby-position’
region-breakgets folded into the new property, too.
@charsetparsing rules from CSS3 to CSS2.1. dbaron to propose errata; zcorpan to update tests.
:has()with some previous-child and -parent combinators in fast profile. There were still a lot of concerns about the performance implications. dbaron will test to see what the effects would be so that a more informed decision can be made.
::markerto pseudo-elements spec, takes properties from color module and fonts module (color, font-*, and opacity)
::markerwith font properties and color to pseudo-elements spec (and still plan to do more later in the lists spec).
text-wrap: balanceproposal, there was some concern about the inheritance behavior. Instead, they will work on creating
white-spaceproperties were well received, though it was thought that discard would be a better word than consume.
region-fragmentreceived the most attention for bikeshedding. One issue with
continueis that it is a verb when almost all property names have been nouns or adjectives. Some people were inclined to return the name to
fragmentationbut most of the group felt that would have no context outside of the working group. It was suggested that there was likely vocabulary for this concept and that users of programs like inDesign or PhotoShop would likely have some suggestions.
region-fragmentproperties defined outside the overflow context. It was agreed thought they are similar, they’re not the same and therefore should be separate.
allisn’t viewed as particularly accessible since it removes the
:focusoutline on an element. Consensus was the old
defaultthat was removed from the spec would fix the problem. The spec authors will go back and see if there are any reasons that
defaultwas removed that need to be addressed and re-introduce next week for formal resolution.
.icoto the web consortium.
.icoare the standards and they will be expected in new products. It’s an informative note. It will be up to the person writing the note as to what exactly goes inside.
imageCSS value, as well as SVG if the implementation supports SVG and saying for cursor that all non animated formats supported for
imageMUST be supported in cursor, and that all animated formats supported in
imageSHOULD be supported in cursor. However, Microsoft asked for a week to review, so formal resolution will be asked for on next week’s call.
trailing-spaceswill be in CSS Text Level 4
The CSS WG has published an updated Working Draft of the CSS Fragmentation Module Level 3. This module describes the fragmentation model that partitions a flow into pages, columns, or regions and provides controls for breaking.
We expect this to be the last WD before CR, and plan to transition at the end of March. Please review and send us any comments. If you plan to review but aren’t sure you have time, send us a note so that we know to wait for your comments.
We are particularly looking for feedback on
We are particularly looking for reviews from
We also welcome any submissions of better/more examples and diagrams.
As always, please send feedback to the (archived) public mailing list email@example.com with the spec code (
[css-break]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
@supportsto Cascade Level 4
border-start-end-radius(in CSS Logical Properties)
contentas the new value for
no-wrapas an alias to
nowrapto alleviate author confusion. However, the group remained unconvinced as to if it was the best way forward. This issue will remain open while the group explores more possibilities and looks for more information.
break-*properties to control inline layout. It received a warm reception as an idea worth exploring.
text-wrap: balanceproposal was also well received with a lot of people showing interest in developing it further.
ime-modeas obsolete as described in the draft of CSS3 UI
ime-modeto say browsers “should not” support, however that wasn’t resolved upon so the previously resolved upon publication will go forward with the existing language and the “should not” language will wait for a formal resolution.
nav-*properties from CSS3 UI might help address some of the issues.
justify-contenton grid containers operate on the grid tracks (allows distributing extra space between grid tracks)
Browse by date:
Browse by category: