(In reply to szager from comment #3) > I'm currently implementing context-fill and context-stroke support for chromium (https://crbug.com/367737) This is kind of a side point, but... Why? I'm not sure you want to do that... Our intent is (and has always been) that `context-fill` and `context-stroke` would be ripped out and replaced by the standardized (but not-yet-implemented) version that ultimately arrived in bug 1812163. That's the whole reason these properties are internal-only in Firefox -- the were good enough to serve a narrow purpose that we needed, but they weren't sufficiently general to be something we'd advocate baking into the web platform. Bug 1812163 captures the "better" version that we settled on (though we still need to implement it). And we made them internal-only so that we'd have the ability to do a search-and-replace on a limited number of repos to modernize to the new thing, once we've got it ready, and then we can safely rip out the old thing.
Bug 1881943 Comment 10 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to szager from comment #3) > I'm currently implementing context-fill and context-stroke support for chromium (https://crbug.com/367737) This is kind of a side point, but... Why? I'm not sure you want to do that... Our intent is (and has always been) that `context-fill` and `context-stroke` would be ripped out and replaced by the standardized (but not-yet-implemented) version that we had in our heads for a while and ultimately arrived (in spec form for now) in bug 1812163. That's the whole reason these properties are internal-only in Firefox -- the were good enough to serve a narrow purpose that we needed, but they weren't sufficiently general to be something we'd advocate baking into the web platform. Bug 1812163 captures the "better" version that we settled on (though we still need to implement it). And we made them internal-only so that we'd have the ability to do a search-and-replace on a limited number of repos to modernize to the new thing, once we've got it ready, and then we can safely rip out the old thing.
(In reply to szager from comment #3) > I'm currently implementing context-fill and context-stroke support for chromium (https://crbug.com/367737) This is kind of a side point, but... Why? I'm not sure you want to do that... Our intent is (and has always been) that `context-fill` and `context-stroke` would be ripped out and replaced by the standardized (but not-yet-implemented) version that we had in our heads for a while and ultimately arrived (in spec form for now) in bug 1812163. That's the whole reason these properties are internal-only in Firefox -- the were good enough to serve a narrow purpose that we needed, but they weren't sufficiently general to be something we'd advocate baking into the web platform. Bug 1812163 captures the "better" version that we settled on (though we still need to implement it). And we made them internal-only so that we'd have the ability to do a search-and-replace on a limited number of repos to modernize to the new thing, once we've got it ready, and then we can safely rip out the implementation of the old/internal thing.