The design doc doesn't give a lot of background. Can you provide a short
explanation or an inline explainer as to what this is trying to solve and
how we think developers will be using this? Thanks! :)

On Fri, Aug 30, 2024 at 7:10 PM Wenyu Fu <weny...@chromium.org> wrote:

> > The work isn't being done by the team which owns Blink>CSS so it would
> be good if there were experts which could triage incoming bugs, etc in this
> area.
>
> Good callout! I can't seem to find an appropriate component for this
> feature, thus I choose the closest. During development I've been closely
> working with owners from Blink>CSS (futhark@) and I think this still fits
> the CSS area.
>
> FWIW I think we could still create the Blink>CSS>SafeArea component
>
> > make public access to the indicated document?
>
> Sorry for the inconvenience. The original doc is associated with my google
> account, and I have trouble sharing it to the public.
> I've made a public copy:
> https://docs.google.com/document/d/1VL0KNzdQwATk9Uf8kP0kcbO1-dDx86pPvB_bMQdLLHE/edit
>
> On Thu, Aug 29, 2024 at 11:53 PM uazo <carmelo.mess...@gmail.com> wrote:
>
>> > Design docs
>>
>> could you make public access to the indicated document?
>>
>> thank you!
>>
>> On Thursday, August 29, 2024 at 9:09:17 PM UTC+2 ikilp...@chromium.org
>> wrote:
>>
>>> On Thu, Aug 29, 2024 at 12:00 PM Wenyu Fu <wen...@chromium.org> wrote:
>>>
>>>> Contact emailswen...@chromium.org, wen...@google.com
>>>>
>>>> ExplainerNone
>>>>
>>>> Specificationhttps://developer.mozilla.org/en-US/docs/Web/CSS/env
>>>>
>>>> Design docs
>>>>
>>>> https://docs.google.com/document/d/1Wg8M-tkeo7_JDRYVV2vB22pAPQMYXuJ2Ik-fmqn-plg/edit?tab=t.0
>>>>
>>>> Summary
>>>>
>>>> Dynamically change the safe area inset based on the shown ration for
>>>> the browser controls. This is used when to keep the web contents from the
>>>> display cutout area when Chrome is drawing edge to edge. This feature is
>>>> targeting Android only. Similar browser behavior is already available for
>>>> Chrome on iOS and Safari Mobile. Detailed design & implementation, please
>>>> see crbug.com/324436581
>>>>
>>>>
>>>> Blink componentBlink>CSS
>>>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ECSS>
>>>>
>>>>
>>> Could we create a new Blink component for the env(safe-area-*)
>>> implementation? (Maybe Blink>SafeArea).
>>>
>>> The work isn't being done by the team which owns Blink>CSS so it would
>>> be good if there were experts which could triage incoming bugs, etc in this
>>> area.
>>>
>>>
>>>> Search tagssafearea <https://chromestatus.com/features#tags:safearea>
>>>>
>>>> TAG reviewNone
>>>>
>>>> TAG review statusNot applicable
>>>>
>>>> Risks
>>>>
>>>>
>>>> Interoperability and Compatibility
>>>>
>>>> None
>>>>
>>>>
>>>> *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?
>>>>
>>>> No specific behavior changes to API, no impact to WebView.
>>>>
>>>>
>>>> Debuggability
>>>>
>>>> None
>>>>
>>>>
>>>> Will this feature be supported on all six Blink platforms (Windows,
>>>> Mac, Linux, ChromeOS, Android, and Android WebView)?No
>>>>
>>>> Android only - feature targeting OS with a browser controls.
>>>>
>>>>
>>>> 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://flagsdynamic-safe-area-insets,
>>>> dynamic-safe-area-insets-on-scroll
>>>>
>>>> Finch feature nameDynamicSafeAreaInsets, DynamicSafeAreaInsetsOnScroll
>>>>
>>>> Requires code in //chrome?False
>>>>
>>>> Tracking bughttps://g-issues.chromium.org/issues/324436581
>>>>
>>>> Launch bughttps://launch.corp.google.com/launch/4339772
>>>>
>>>> MeasurementNo specific measurement on web platform. This success will
>>>> be measured together with https://launch.corp.google.com/launch/4339772
>>>>
>>>> Availability expectationFeature is already available on Safari, and is
>>>> implemented to make available on Chrome on Android.
>>>>
>>>> Adoption expectationNo change is required from web developer.
>>>>
>>>> Adoption planNo changes needed from the developer.
>>>>
>>>> Non-OSS dependencies
>>>>
>>>> Does the feature depend on any code or APIs outside the Chromium open
>>>> source repository and its open-source dependencies to function?
>>>> No
>>>>
>>>> Sample links
>>>>
>>>> https://screencast.googleplex.com/cast/NTMyMTc4MzcyODE0NDM4NHxmOGViYjdmMC1iZg
>>>>
>>>> Estimated milestones
>>>> Shipping on Android 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).
>>>> No anticipated spec change at the scope for this launch.
>>>>
>>>> Link to entry on the Chrome Platform Status
>>>> https://chromestatus.com/feature/5174306712322048?gate=5101473814544384
>>>>
>>>> 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+...@chromium.org.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFtDRbBh16No8Jsge-tsaxfXsYOauJVkW4cxsVJQkJ_-2hFAww%40mail.gmail.com
>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFtDRbBh16No8Jsge-tsaxfXsYOauJVkW4cxsVJQkJ_-2hFAww%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/CAFtDRbDYE2m%3Do-ddaJZc1CvN5FL4jHRbS_fo8T4mfc8tvwk6OA%40mail.gmail.com
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFtDRbDYE2m%3Do-ddaJZc1CvN5FL4jHRbS_fo8T4mfc8tvwk6OA%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/CAOmohSLMn-0CQ4%2B26bw63nMZ2x45uONsGsaj9awDaNdBwkkmHA%40mail.gmail.com.

Reply via email to