On Wed, Jul 10, 2024 at 6:10 PM 'Ajay Rahatekar' via blink-dev <
blink-dev@chromium.org> wrote:

> Contact emailsmas...@chromium.org
>
> ExplainerNone
>
> Specification
> https://github.com/w3c/csswg-drafts/issues/10209#issuecomment-2221005001
>
> Summary
>
> The CSSWG resolved to rename the `inset-area` property to `position-area`.
> See the CSSWG discussion here:
> https://github.com/w3c/csswg-drafts/issues/10209#issuecomment-2221005001.
> The new property name, `position-area`, as a synonym for `inset-area`
> shipped via https://chromestatus.com/feature/6567965055778816. This entry
> is for deprecation and removal of the `inset-area` property.
>
>
> Blink componentBlink>CSS
> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ECSS>
>
> Motivation
>
> With the CSSWG resolution on renaming the property to `position-area`,
> this deprecation will clean up the implementation in Chromium for a
> standards compliant feature.
>
>
> Initial public proposalNone
>
> Search tagsanchor positioning
> <https://chromestatus.com/features#tags:anchor%20positioning>
>
> TAG reviewNone
>
> TAG review statusNot applicable
>
> Risks
>
>
> Interoperability and Compatibility
>
> None
>

>From the other emails, there is a 0.02% usage of this property right now,
so it may be worthwhile to document the planned timeline for the
rename process.

This lists M131 as the shipping milestone, but I assume we want to do this
before then, right?

Thanks,
Vlad



>
>
> *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
>
>
> Is this feature fully tested by web-platform-tests
> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
> ?No
>
> Flag name on chrome://flagsNone
>
> Finch feature nameNone
>
> Non-finch justificationNone
>
> Requires code in //chrome?False
>
> Tracking bughttps://crbug.com/352360007
>
> Estimated milestones
> Shipping on desktop 131
> DevTrial on desktop 129
> Shipping on Android 131
> DevTrial on Android 129
> Shipping on WebView 131
>
> Link to entry on the Chrome Platform Status
> https://chromestatus.com/feature/5944933945704448?gate=6046273227718656
>
> 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/CAHB%2BDAhbysWX2rT2QGMiv%3D2XvxYD9pzKTy894OFP81RNoPHKMg%40mail.gmail.com
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHB%2BDAhbysWX2rT2QGMiv%3D2XvxYD9pzKTy894OFP81RNoPHKMg%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/CADsXd2ODg%2Bo9UiMK4N6aB%2BTFMwAOEPgnUDgHk74jzjkpRMar5Q%40mail.gmail.com.

Reply via email to