Mark !important values for supported properties in @position-try as invalid
Categories
(DevTools :: Inspector: Rules, task, P3)
Tracking
(firefox147 fixed, firefox148 fixed)
People
(Reporter: nchevobbe, Assigned: nchevobbe)
References
(Blocks 1 open bug)
Details
Attachments
(4 files, 1 obsolete file)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
From https://drafts.csswg.org/css-anchor-position-1/#fallback-rule:
It is invalid to use !important on the properties in the <declaration-list>. Doing so causes the property it is used on to become invalid, but does not invalid the @property-try rule as a whole.
Updated•7 months ago
|
| Assignee | ||
Updated•6 months ago
|
| Assignee | ||
Updated•6 months ago
|
| Assignee | ||
Comment 1•6 months ago
|
||
In some cases, a declaration will be valid for a rule type, and not for another
rule type. At the moment, InspectorUtils.supports will only watch the validity
of the passed string for CssRuleType::Style.
This patch adds a rule option to SupportsOptions, from which we then
extract its type and pass it to Servo_CSSSupports so we can check the validity
of a string against a specific rule type.
Test cases are added in layout/inspector/tests/test_supports.html.
Updated•6 months ago
|
| Assignee | ||
Comment 2•6 months ago
|
||
This will make it possible to check the validity of a declaration for a specific rule,
for example, we'll be able to detect !important invalid declaration value in @position-try rules.
| Assignee | ||
Comment 3•6 months ago
|
||
The assertion was hard to parse and not working as expected.
Updated•6 months ago
|
Comment 4•6 months ago
|
||
Comment on attachment 9531077 [details]
Bug 1895179 - Add rule SupportsOptions for InspectorUtils.supports to check support for a given rule type. r=#layout-reviewers.
Revision D275192 was moved to bug 2004379. Setting attachment 9531077 [details] to obsolete.
Comment 6•6 months ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/c2fb7edc024a
https://hg.mozilla.org/mozilla-central/rev/85db22e38540
| Assignee | ||
Comment 7•6 months ago
|
||
The assertion was hard to parse and not working as expected.
Original Revision: https://phabricator.services.mozilla.com/D275228
Updated•6 months ago
|
Comment 8•6 months ago
|
||
firefox-beta Uplift Approval Request
- User impact if declined: This stack of patches adds minimal DevTools support for
@position-tryrules, which are part of Anchor positioning, which was enabled by default in 147.
Without this, users might think that the implementation is incomplete and that@position-tryis not supported. - Code covered by automated testing: yes
- Fix verified in Nightly: no
- Needs manual QE test: no
- Steps to reproduce for manual QE testing: -
- Risk associated with taking this patch: low
- Explanation of risk level: This is DevTools only, covered by tests.
Even though this is not a small change, we're not doing anything extraordinarily new, mostly just adding on existing mechanism in DevTools - String changes made/needed:
inactive-css-at-position-try-not-supportedwas added - Is Android affected?: yes
| Assignee | ||
Comment 9•6 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D275193
Updated•6 months ago
|
Updated•6 months ago
|
Updated•6 months ago
|
Updated•6 months ago
|
Comment 10•6 months ago
|
||
| uplift | ||
Description
•