Thank you all.

On Thu, Jul 11, 2024 at 11:48 AM Mike Taylor <[email protected]> wrote:

> LGTM3
> On 7/11/24 2:18 PM, Chris Harrelson wrote:
>
> LGTM2
>
> On Thu, Jul 11, 2024 at 11:06 AM Vladimir Levin <[email protected]>
> wrote:
>
>> LGTM1 to add `position-area`, since it is an alias for `inset-area` that
>> is shipped and is being deprecated.
>>
>> On Thu, Jul 11, 2024 at 12:22 PM Mason Freed <[email protected]> wrote:
>>
>>>
>>> On Thu, Jul 11, 2024 at 9:17 AM Vladimir Levin <[email protected]>
>>> wrote:
>>>
>>>> Just to clarify: this intent is to add `position-area` which is a drop
>>>> in replacement/alias for `inset-area`. The latter is being deprecated via
>>>> another intent. Is this correct?
>>>>
>>>
>>> That's exactly right, yes. The intent to deprecate the old name
>>> (inset-area) is this one
>>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/SLOin9wVpZA/m/WJkEz6faAwAJ>
>>> .
>>>
>>> Thanks,
>>> Mason
>>>
>>>
>>>
>>>> Thanks,
>>>> Vlad
>>>>
>>>> On Wed, Jul 10, 2024 at 6:23 PM Mason Freed <[email protected]>
>>>> wrote:
>>>>
>>>>> {NOTE: this is a replacement of this chromestatus
>>>>> <https://chromestatus.com/feature/6567965055778816>, which has the
>>>>> wrong feature type and cannot be changed.}
>>>>> Contact emails [email protected]
>>>>>
>>>>> Explainer None
>>>>>
>>>>> Specification
>>>>> https://github.com/w3c/csswg-drafts/issues/10209#issuecomment-2221005001
>>>>>
>>>>> Summary
>>>>>
>>>>> The CSSWG resolved to rename this property from `inset-area` to
>>>>> `position-area`. See the CSSWG discussion here:
>>>>> https://github.com/w3c/csswg-drafts/issues/10209#issuecomment-2221005001
>>>>> Chrome disagrees with this change, but would like to ship an interoperable
>>>>> implementation. We will ship the new property name, `position-area`, as a
>>>>> synonym for `inset-area` first. Then after a suitable amount of time, we
>>>>> will remove `inset-area`. The latter removal will be done under a separate
>>>>> Intent.
>>>>>
>>>>>
>>>>> Blink component Blink>CSS
>>>>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ECSS>
>>>>>
>>>>> TAG review None
>>>>>
>>>>> TAG review status Not applicable
>>>>>
>>>>> Risks
>>>>>
>>>>>
>>>>> Interoperability and Compatibility
>>>>>
>>>>> There is a compat risk with this rename, since the old name of
>>>>> `inset-area` is in use, with an 0.02% use counter:
>>>>> https://chromestatus.com/metrics/css/timeline/popularity/781 We will
>>>>> need to ship the new name, `position-area`, first, and issue deprecation
>>>>> warnings for the old name, `inset-area`, to give developers time to 
>>>>> change.
>>>>> This intent to ship is about shipping `position-area` as a synonym for
>>>>> `inset-area`. We'll issue a separate I2D for removing the `inset-area`
>>>>> property.
>>>>>
>>>>>
>>>>> *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://flags None
>>>>>
>>>>> Finch feature name None
>>>>>
>>>>> Non-finch justification None
>>>>>
>>>>> Requires code in //chrome? False
>>>>>
>>>>> Estimated milestones
>>>>> Shipping on desktop 129
>>>>> DevTrial on desktop 129
>>>>> Shipping on Android 129
>>>>> DevTrial on Android 129
>>>>> Shipping on WebView 129
>>>>>
>>>>> 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/5142143019253760?gate=5177831244693504
>>>>>
>>>>> 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/CAM%3DNeDjpLLJ-0pd%2BhJCUPnqGo63NPNV4SsXEJQh5DLucCT_2vA%40mail.gmail.com
>>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM%3DNeDjpLLJ-0pd%2BhJCUPnqGo63NPNV4SsXEJQh5DLucCT_2vA%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 [email protected].
>>> To view this discussion on the web visit
>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM%3DNeDjOj8rF89tC3c%2BjYSp7tvOkbF-3jup6ntShhUpohERddA%40mail.gmail.com
>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM%3DNeDjOj8rF89tC3c%2BjYSp7tvOkbF-3jup6ntShhUpohERddA%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 [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADsXd2O%3D5yCOEvzXqzA7Gx34W_Xm7Z3M1Tqyvi93qwnn3t9eCg%40mail.gmail.com
>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADsXd2O%3D5yCOEvzXqzA7Gx34W_Xm7Z3M1Tqyvi93qwnn3t9eCg%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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw__Ndw7ns3NHpZrrg27Wo_Dy8yM-7639NCAsnPnxGYVtQ%40mail.gmail.com
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw__Ndw7ns3NHpZrrg27Wo_Dy8yM-7639NCAsnPnxGYVtQ%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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM%3DNeDj1oV_54-LvxszGEbhtx-uS9mAspPpK8QiwwzvwN6WAgg%40mail.gmail.com.

Reply via email to