On 3/14/24 6:29 PM, Stefan Zager wrote:



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?

According to our process, we either need to request a TAG review, or explain why we think it doesn't require a TAG review. But I've just reminded myself of the exceptions at https://www.chromium.org/blink/guidelines/api-owners/process-exceptions/ - and I think you're good given the first exemption.



            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.

I think it serves as a good signal that WebKit should prioritize shipping here as well, if they'll be the only engine without support - and if they have strong feelings as to why something should change before we do ship it, now is the time for them to provide that input before it's too late.


    /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.

Can you explain why you think this should be exempt, per https://chromium.googlesource.com/chromium/src/+/main/docs/flag_guarding_guidelines.md?

In the future, you can avoid these kinds of questions if you give a little bit more justification. :)


            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/3c773a18-183c-4094-91f3-79e7948b9364%40chromium.org.

Reply via email to