I've obsoleted this chromestatus entry, and created a fresh one with the
correct (I think) feature type. I have sent a fresh I2S on that entry.
Please disregard this one.

Thanks,
Mason

On Wed, Jul 10, 2024 at 9:12 AM Mason Freed <[email protected]> wrote:

>
>
> On Wed, Jul 3, 2024 at 3:02 AM Yoav Weiss (@Shopify) <
> [email protected]> wrote:
>
>> Note: They can preemptively handle this change today by using
>>> position-try:flip-inline instead.
>>>
>>>
>>>> It's tricky, because waiting could actually cause *more* breakage,
>>>> even with a deprecation period, and the numbers look quite good right now.
>>>>
>>>
>> If the app in question could switch to `position-try:flip-inline` that
>> changes things, and would indeed not require a milestone overlap, assuming
>> they can make that change.
>>
>
> I've received the contact info privately, and I'll reach out to the
> affected app. Assuming that goes well, it sounds like we might be ok
> shipping a direct rename?
>
> Thanks,
> Mason
>
>
>>
>>>
>>>>
>>>>
>>>>
>>>> *Gecko*: No signal
>>>>
>>>> *WebKit*: No signal
>>>>
>>>> *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
>>>>
>>>> https://wpt.fyi/results/css/css-anchor-position
>>>>
>>>>
>>>> Flag name on chrome://flagsNone
>>>>
>>>> Finch feature nameNone
>>>>
>>>> Non-finch justificationNone
>>>>
>>>> Requires code in //chrome?False
>>>>
>>>> Tracking bughttps://crbug.com/349600667
>>>>
>>>> Estimated milestonesShipping on desktop128Shipping on Android128Shipping
>>>> on WebView128
>>>>
>>>> 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 Statushttps://chromestatus.com/
>>>> feature/5167414571696128?gate=5182169462079488
>>>>
>>>> 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 [email protected].
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/cf8a8c9d-9efa-4bff-9dd5-590809fe2877n%40chromium.org
>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/cf8a8c9d-9efa-4bff-9dd5-590809fe2877n%40chromium.org?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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM%3DNeDiutdqP8jNJSH_r%2BZRt85N8BfVwxY%2BzhoqJfuVjcX1ozA%40mail.gmail.com.

Reply via email to