Closed
Bug 1686585
Opened 5 years ago
Closed 5 years ago
[Inactive CSS] Display a warning when 'paint-order' is used on incorrectly
Categories
(DevTools :: Inspector: Rules, enhancement, P5)
DevTools
Inspector: Rules
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: sebo, Unassigned)
References
(Blocks 1 open bug)
Details
+++ This bug was initially created as a clone of Bug #1686583 +++
As of SVG 2, CSS Fill and Stroke, and bug 1435684, paint-order can only be applied to SVG basic shapes, SVG text elements, and HTML elements.
Currently, for HTML elements you additionally need to specify -webkit-text-stroke (or its longhand properties).
Main file:
devtools/server/actors/utils/inactive-property-helper.js
invalidProperties: ["paint-order"]
Translation strings:
devtools/client/locales/en-US/tooltips.ftl
inactive-css-only-svg-shapes = <strong>{ $property }</strong> has no effect on this element since it can only be applied to SVG basic shapes, SVG text elements, or HTML elements, though it may have an effect on its descendant elements.
inactive-css-only-svg-shapes-fix = For HTML elements, try setting <strong>-webkit-text-stroke<strong> to something other than <strong>0px</strong>, otherwise ensure you are setting this property on one of the following SVG elements: <strong><circle></strong>, <strong><ellipse></strong>, <strong><line></strong>, <strong><path></strong>, <strong><polygon></strong>, <strong><polyline></strong>, <strong><rect></strong>, <strong><text></strong>, <strong><textPath></strong>, <strong><tspan></strong>. { learn-more }
Sebastian
| Reporter | ||
Updated•5 years ago
|
Summary: [Inactive CSS] Display a warning when 'fill-rule', 'marker-*' or 'shape-rendering' are used on invalid elements → [Inactive CSS] Display a warning when 'paint-order' is used on incorrectly
Comment 1•5 years ago
|
||
Per my notes in bug 1583901 comment 9 onwards, and the code-comment added in bug 1688538: we shouldn't actually add a warning about this property, because it's inherited-by-default, which makes it hard to reason about whether it's truly inactive (in the element's whole subtree) or not.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•