This is a tracking task for expanding the grammar.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T269044 Support more CSS properties / rules in css-sanitizer | |||
| Open | BUG REPORT | None | T265675 RGBA hexadecimal value is not supported in background-color (no support for transparency value) | ||
| Open | None | T255343 Support overflow-wrap: anywhere | |||
| Open | None | T255342 Support for linear-gradient | |||
| Open | None | T241946 Support @media (prefers-color-scheme: ...) rule | |||
| Open | None | T238690 Add support for background-position-x and y | |||
| Open | None | T222678 Add image-rendering to cssImage3 set | |||
| Open | None | T217722 Support (part of?) Selectors level 4 in css-sanitizer | |||
| Open | None | T162379 Decide which non-standard CSS properties to support in TemplateStyles | |||
| Open | None | T216897 Add 'width: -webkit-fill-available' to allowed syntax for TemplateStyles | |||
| Open | None | T271598 Allow use of scroll-margin-top in TemplateStyles |
Event Timeline
Comment Actions
Which actual planning/organizing problem does this tracking task solve, which outweighs the need to have someone watch incoming css-sanitizer tasks and remember this task to add them as subtasks?
Comment Actions
Do tracking tasks provide any value independent of the subtasks they track? To me the name kind of implies that the value is in the act of tracking, ie. being able to categorize those tasks.
Comment Actions
Do tracking tasks provide any value independent of the subtasks they track?
@Tgr: As tracking tasks in Bugzilla were what projects are in Phab, projects allow categorizing tasks related to the same codebase or scope. Tasks have a status field, so tasks should have criteria when they could be considered resolved. See also https://www.mediawiki.org/wiki/Phabricator/Help#.22Tracking.22_tasks
Do you think there is a need for a "More css properties / rules" subproject under css-sanitizer as you seem to see a need for categorization?
Comment Actions
I honestly don't think this task is needed for the purposes of tracking. There are only a dozen tasks in css-sanitizer and its job should almost exclusively be "add new CSS support" given the fairly successful rollout of the primary-using extension, which is TemplateStyles. All the tasks tracked by this one are also in this project. I do think one or two could maybe stand to have a few other projects. I almost feel like css-sanitizer should be a subproject of TemplateStyles; is it used elsewhere (should it be?)?
What could maybe be done with this task is to get it assigned to the patch tgr identified in T268955#6657404 and then either flip the dependencies on this task to parents rather than children, or if the megapatch doesn't yet include some functionality identified, potentially break the link.
Comment Actions
If we really think there is a need to track these otherwise, a "(New) Properties Backlog" column on css-sanitizer would also do.