[meta] CSS priorities 2019
Categories
(Core :: Layout, enhancement)
Tracking
()
People
(Reporter: tantek, Unassigned)
References
(Depends on 5 open bugs, )
Details
(Keywords: meta)
This bug is for tracking and discussing (along with https://wiki.mozilla.org/CSS#Platform_priorities longer term) Layout team priorities for implementing CSS specs in 2018. This is a meta bug, feel free to add the meta bugs for specific CSS specs you'd like to see us finish (or make measurable / whole features progress on) in 2018. If you're not sure, feel free to comment which specs you think should be considered. We'll be discussing/iterating on this at #yallhands.
|
Reporter | |
Comment 1•6 years ago
|
||
Add *as dependent* bugs. If there are specific CSS features (properties, values, @-rules, selectors etc.) you'd like to call out for 2018 instead of their whole spec/modules, feel free to add those directly as dependent bugs.
|
||
Comment 2•6 years ago
|
||
The wiki page links to several bugs targeted this year. I guess they should be added as blockers to this bug, so progress on them can be tracked, right? Sebastian
|
|
||
Updated•6 years ago
|
|
|
Reporter | |
Comment 3•5 years ago
|
||
Making this a meta-bug for ongoing tracking of dependent bugs (next 12 months). Updating wiki page first in coordination with Layout planning. We can add high priority (P1) items as blockers to this bug for tracking purposes. Thanks!
|
|
||
Comment 4•5 years ago
|
||
With P1, do you mean the "Importance" field to be P1 (because, as far as I know, P1 is only meant for critical bugs) or the bugs to have "[layout:p1]" as whiteboard tag, or something else? Are they already prioritized? The wiki page still seems to be in an interim state. Any way to provide input for the priorities? Sebastian
|
|
||
Comment 5•5 years ago
|
||
As we are already more than half-way through the year, I went ahead and added some bugs as blockers for this one looking at the priority list in the wiki and the bugs marked as "[layout:p1]". I also renamed this bug in order to reflect that these are now the priorities for 2019.
Having said that, the wiki page is obviously outdated and Tantek doesn't seem to be active anymore. So, could someone from the layout team please revise the wiki page and add or remove bugs blocking this one accordingly?
Sebastian
|
|
||
Comment 6•5 years ago
|
||
Subgrid and motion paths also seem to be priorities, as people are actively working on them, so I've added them as blockers.
Sebastian
|
|
||
Comment 7•2 years ago
|
||
It's almost 2022, so I finally close this one. Would be good to know what the CSS priorities are for next year. Is there any public reference for that?
Sebastian
|
||
Comment 8•2 years ago
•
|
||
Thanks! Yeah, makes sense to close this tracking-bug out - thanks for doing that.
I don't know that we've published a list of CSS priorities for next year (some of that is still to be determined at some point early in the new year). I'm not sure if we'll file a metabug or publish any explicit "here are our plans for the whole year" kind of thing (some of it our plans will likely be tentative & subject-to-change); but at a minimum you can keep an eye on intent-to-implement/intent-to-ship posts on dev.platform to see what's coming or in-progress.
|
|
||
Comment 9•2 years ago
|
||
Hi Daniel,
Thank you for the info! Of course things can change during the year. If you publish a rough plan of things you plan to implement 2022 at some point, though, or at least the upcoming months, please let me know!
I already follow all intent-to-implement/intent-to-ship posts and also many of the CSS related bugs, so I do have some idea of what's coming next. Though I believe that there are more people than just me interested in a longer-term strategy related to CSS. And previously you had bugs like this one, https://wiki.mozilla.org/CSS and https://wiki.mozilla.org/GeckoGoalsfor2021#CSS, which provided a bit of a plan.
Anyway, I wish you all Happy Holidays!
Sebastian
Description
•