Proposed W3C Charter: CSS Working Group
The W3C is proposing a revised charter for: Cascading Style Sheets (CSS) Working Group https://www.w3.org/2019/08/proposed-css-2019.html https://lists.w3.org/Archives/Public/public-new-work/2019Aug/0015.html The differences from the previous charter are: https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2FStyle%2F2016%2Fcss-2016.html=https%3A%2F%2Fwww.w3.org%2F2019%2F08%2Fproposed-css-2019.html Mozilla has the opportunity to send comments or objections through Sunday, September 22. (Sorry for delaying sending this for so long!) Please reply to this thread if you think there's something we should say as part of this charter review, or if you think we should support or oppose it. -David -- 턞 L. David Baron http://dbaron.org/ 턂 턢 Mozilla https://www.mozilla.org/ 턂 Before I built a wall I'd ask to know What I was walling in or walling out, And to whom I was like to give offense. - Robert Frost, Mending Wall (1914) ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Proposed W3C Charter: CSS Working Group
On Monday 2016-08-29 17:21 -0700, L. David Baron wrote: > The W3C is proposing a revised charter for: > > Cascading Style Sheets (CSS) Working Group > https://www.w3.org/Style/2016/css-2016.html > https://lists.w3.org/Archives/Public/public-new-work/2016Aug/.html > > Mozilla has the opportunity to send comments or objections through > this Friday, September 2. > > Please reply to this thread if you think there's something we should > say as part of this charter review, or if you think we should > support or oppose it. Nobody else replied, so I wrote the following (the deadline was extended to today): While the CSS WG continues to produce a number of important specifications, it has remained weak at getting good input from all of the relevant constituencies. This isn't necessarily something that the charter can fix, but I think it is worth pointing out. Some impromevents that would help with this are fixing some of the problems that scare participants away; for example, spending large meetings on very technical details that many people aren't interested in, thus scaring off people who have important things to say about bigger-picture issues but aren't interested in the most detailed discussions. (This may even be helped by improvements already present in this charter.) Some of the more speculative Houdini specs are not listed as deliverables in the charter, but it seems they should be. (CSS Layout API, Box Tree API, and maybe also CSS Parser API and Font Metrics API) I also *think* the group has agreed to rename the Motion Path spec (listed in the charter as motion-1) as part of merging its uses with some requirements for CSS Round Display; the charter should be updated to reflect the new name (which I don't currently recall). I'm also not entirely happy about the implication of the sentence "This avoids waiting for the next weekly call, if consensus can be determined before then." in the Decision Policy section; it seems to imply that the only value of asynchronous decision making is to make decisions faster. Asynchronous decision making can also help to include those who would be left out by a synchronous decision making process. I think it would be an improvement to just drop the sentence. -David -- 턞 L. David Baron http://dbaron.org/ 턂 턢 Mozilla https://www.mozilla.org/ 턂 Before I built a wall I'd ask to know What I was walling in or walling out, And to whom I was like to give offense. - Robert Frost, Mending Wall (1914) signature.asc Description: PGP signature ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Proposed W3C Charter: CSS Working Group
The W3C is proposing a revised charter for: Cascading Style Sheets (CSS) Working Group https://www.w3.org/Style/2016/css-2016.html https://lists.w3.org/Archives/Public/public-new-work/2016Aug/.html Mozilla has the opportunity to send comments or objections through this Friday, September 2. Please reply to this thread if you think there's something we should say as part of this charter review, or if you think we should support or oppose it. -David -- 턞 L. David Baron http://dbaron.org/ 턂 턢 Mozilla https://www.mozilla.org/ 턂 Before I built a wall I'd ask to know What I was walling in or walling out, And to whom I was like to give offense. - Robert Frost, Mending Wall (1914) signature.asc Description: PGP signature ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Proposed W3C Charter: CSS Working Group
The W3C is proposing a revised charter for: Cascading Style Sheets (CSS) Working Group http://lists.w3.org/Archives/Public/public-new-work/2014May/.html http://www.w3.org/Style/2013/css-charter.html deadline for comments: May 29 Mozilla has the opportunity to send comments or objections through May 29. Please reply to this thread if you think there's something we should say. As with charters for other long-lived groups, the details in the list of deliverables largely matter only in that they might constrain what the group is allowed to work on without a new charter; the dates tend to be largely fiction. My intent (unless I get other comments) is to support the charter, but point to comments that have been made on the working group mailing list since the charter was sent out for review (some of which are about documents omitted from the list) so that the W3C has a chance to incorporate those comments (which it probably wouldn't if no AC representative mentioned them). -David -- 턞 L. David Baron http://dbaron.org/ 턂 턢 Mozilla https://www.mozilla.org/ 턂 Before I built a wall I'd ask to know What I was walling in or walling out, And to whom I was like to give offense. - Robert Frost, Mending Wall (1914) ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Proposed W3C Charter: CSS Working Group
I'd really like to see the CSS WG spend some time on properties that allowed more control over scrolling and zooming. Also something that addresses the complexity involved in building long scrollable lists. Right now a lot of websites implement their own scrolling behavior in JS by listening to UI events, cancelling their default behavior, and then setting various scroll related values through the DOM. UIs that snap scrolling to certain elements or that implement edge effects can't be done any other way. However this doesn't work well at all as we are moving to a world where scrolling happens off the main thread. Likewise, being able to implement a UI where a user can do zooming currently requires using JS to catch touch/mousewheel events, cancelling them, and then using the DOM to implement a zooming UI. UIs that allow zooming of a part of a webpage, for example zooming in on a picture or an email while leaving surrounding UI intact, can't be implementing right now without main-thread roundtrips. The touch-action CSS property defined in pointer-events attempts to address some of this, but falls far short. The obvious first problem is that it's touch specific (which is sort of ironic given that it's a spec that attempts to remove the separation between touch and mouse input). Finally there's the issue of how to use the DOM and CSS to create a lazily populated list. Currently lazily populating the DOM from a database leads to a lot of churn in reflows of content that's already on the page. These issues are *the* top difficulties on the layout side in creating a performant UI on low end mobile devices. I don't see any deliverables listed in the charter that's attempting to address this. Should we ask that it's added, or is it covered by any of the existing ones? / Jonas On Thu, May 8, 2014 at 5:22 PM, L. David Baron dba...@dbaron.org wrote: The W3C is proposing a revised charter for: Cascading Style Sheets (CSS) Working Group http://lists.w3.org/Archives/Public/public-new-work/2014May/.html http://www.w3.org/Style/2013/css-charter.html deadline for comments: May 29 Mozilla has the opportunity to send comments or objections through May 29. Please reply to this thread if you think there's something we should say. As with charters for other long-lived groups, the details in the list of deliverables largely matter only in that they might constrain what the group is allowed to work on without a new charter; the dates tend to be largely fiction. My intent (unless I get other comments) is to support the charter, but point to comments that have been made on the working group mailing list since the charter was sent out for review (some of which are about documents omitted from the list) so that the W3C has a chance to incorporate those comments (which it probably wouldn't if no AC representative mentioned them). -David -- 턞 L. David Baron http://dbaron.org/ 턂 턢 Mozilla https://www.mozilla.org/ 턂 Before I built a wall I'd ask to know What I was walling in or walling out, And to whom I was like to give offense. - Robert Frost, Mending Wall (1914) ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
