On Thu, Mar 14, 2024, 3:13 PM Mike Taylor <miketa...@chromium.org> wrote:
> On 3/14/24 1:17 PM, Stefan Zager wrote: > > Contact emails sza...@chromium.org > > Explainer None > > Specification https://svgwg.org/svg2-draft/painting.html#context-paint > > Summary > > Implements an existing SVG feature that allows the keywords 'context-fill' > and 'context-stroke' when specifying fill and stroke properties: > https://svgwg.org/svg2-draft/painting.html#context-paint This only > affects SVG sub-trees that are instantiated via a <use> element, and > <marker> elements that are instantiated via the 'marker' property on a > <path> element. In those circumstances, 'context-fill' and 'context-stroke' > are resolved to the value of the 'fill' and 'stroke' properties on the > <use> or <path>. > > > Blink component Blink>SVG > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ESVG> > > TAG review None > > TAG review status Not applicable > > Is there a reason we think a TAG review would not be useful here? > Alternately, has TAG reviewed the SVG2 draft in any capacity before? > I didn't think this merited a TAG review. Do you think it does? > Risks > > > Interoperability and Compatibility > > None > > > *Gecko*: Shipped/Shipping > > Do you happen to know what milestone this shipped in? > I don't know the milestone, but it was in 2017. > > *WebKit*: No signal > > Can we request a signal? > It strikes me as odd to request a position on a mature, long since published spec, but if you think it's appropriate I will do so. > > *Web developers*: No signals > > *Other signals*: > > WebView application risks > > Does this intent deprecate or change behavior of existing APIs, such that > it has potentially high risk for Android WebView-based applications? > > None > > > Debuggability > > None > > > Will this feature be supported on all six Blink platforms (Windows, Mac, > Linux, ChromeOS, Android, and Android WebView)? Yes > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> > ? Yes > > Flag name on chrome://flags None > > Finch feature name None > > Presumably this is behind a feature flag, correct? > No it isn't. Again, I didn't think this merited that kind of treatment. > > Non-finch justification None > > Requires code in //chrome? False > > Launch bug https://issues.chromium.org/issues/40362923 > > Estimated milestones > Shipping on desktop 124 > Shipping on Android 124 > Shipping on WebView 124 > > Anticipated spec changes > > Open questions about a feature may be a source of future web compat or > interop issues. Please list open issues (e.g. links to known github issues > in the project for the feature specification) whose resolution may > introduce web compat/interop risk (e.g., changing to naming or structure of > the API in a non-backward-compatible way). > None > > Link to entry on the Chrome Platform Status > https://chromestatus.com/feature/5146558556536832 > > This intent message was generated by Chrome Platform Status > <https://chromestatus.com/>. > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to blink-dev+unsubscr...@chromium.org. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHOQ7J-4E-nJJ2-pcUUDLxB2pRjOmYF0fKk%2BBjqeXZmuv1uVKw%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHOQ7J-4E-nJJ2-pcUUDLxB2pRjOmYF0fKk%2BBjqeXZmuv1uVKw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHOQ7J-KKc_ib13m5dDuMu1Sj2%2BRe7-N8c1hfa7tWt7MWr%3DQRQ%40mail.gmail.com.
