implement text-outline
Categories
(Core :: CSS Parsing and Computation, enhancement)
Tracking
()
People
(Reporter: rillian, Unassigned)
References
Details
(Keywords: dev-doc-needed)
Comment 1•13 years ago
|
||
Updated•13 years ago
|
Updated•13 years ago
|
| Reporter | ||
Comment 2•12 years ago
|
||
Updated•12 years ago
|
Updated•9 years ago
|
Comment 3•6 years ago
|
||
Is this still relevant? We have -webkit-text-stroke (see bug 1248708 and dependencies), and also paint-order (bug 1435684), which AFAICS should provide the functionality that's requested here.
Updated•3 years ago
|
Comment 4•4 months ago
|
||
In the current spec at https://w3c.github.io/webvtt/#css-extensions, neither text-outline nor -webkit-text-stroke, its standardized counterparts stroke-* from the Fill and Stroke spec, or paint-order apply to WebVTT.
So I think, at this point it makes sense to close this bug and rather file an issue against the WebVTT spec to discuss whether the standardized properties mentioned above should apply.
Emilio, Jonathan, what do you think?
Sebastian
Comment 5•4 months ago
|
||
I think closing this is fine. Authors can already style the WebVTT cues with ::cue and apply these properties, and I don't think they should apply by default FWIW...
Comment 6•1 month ago
•
|
||
(In reply to Emilio Cobos Álvarez [:emilio] from comment #5)
I think closing this is fine. Authors can already style the WebVTT cues with
::cueand apply these properties, ...
As noted earlier, the WebVTT spec currently doesn't allow those properties in ::cue. So I've now filed https://github.com/w3c/webvtt/issues/545 for adding them.
... and I don't think they should apply by default FWIW...
Expressed myself ambiguously. I meant that they should be allowed to be used in ::cue (and its functional variant).
Sebastian
Description
•