LGTM3 that is :)

On Wed, Oct 11, 2023 at 8:55 AM Alex Russell <[email protected]>
wrote:

> Given that the TAG didn't respond in two weeks, I'm going to LGTM1
>
> On Wednesday, October 4, 2023 at 10:50:14 PM UTC-7 Yoav Weiss wrote:
>
>> On Wed, Oct 4, 2023 at 10:27 PM Traian Captan <[email protected]>
>> wrote:
>>
>>> Hi Yoav,
>>>
>>> I don't know of Gecko's and WebKit's concrete implementation plans for
>>> Intersection Observer Scroll Margin.
>>> However, based on their responses on the github issue they were
>>> supportive.
>>>
>>
>> Just wanted to note that we typically ask for official positions on the
>> different vendors standard positions repo.
>> But given the fact that this is a change Mozilla folks requested and
>> Apple folks consistently supported on the issue, I think it's fine to not
>> file those in this case.
>>
>>
>>> Regards,
>>> Traian
>>>
>>>
>>> On Wed, Oct 4, 2023 at 3:46 AM Yoav Weiss <[email protected]>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Tuesday, September 26, 2023 at 1:10:34 AM UTC+2 Traian Captan wrote:
>>>>
>>>> Contact [email protected]
>>>>
>>>> ExplainerNone
>>>>
>>>> Specificationhttps://w3c.github.io/IntersectionObserver/#dom-
>>>> intersectionobserver-scrollmargin
>>>>
>>>> Summary
>>>>
>>>> Intersection Observer scrollMargin allows developers to observe targets
>>>> inside nested scroll containers that are currently clipped away by the
>>>> scroll containers. This is achieved by expanding the container's clipping
>>>> rect by the scrollMargin when calculating the intersection.
>>>>
>>>>
>>>> Blink componentBlink
>>>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink>
>>>>
>>>> Search tagsIntersection Observer
>>>> <https://chromestatus.com/features#tags:Intersection%20Observer>,
>>>> scrollMargin <https://chromestatus.com/features#tags:scrollMargin>
>>>>
>>>> TAG reviewNone
>>>>
>>>> TAG review statusNot applicable
>>>>
>>>> Risks
>>>>
>>>>
>>>> Interoperability and Compatibility
>>>>
>>>> None
>>>>
>>>>
>>>> *Gecko*: Positive (https://github.com/w3c/IntersectionObserver/issues/
>>>> 431)
>>>>
>>>> *WebKit*: Positive (https://github.com/w3c/IntersectionObserver/issues/
>>>> 431)
>>>>
>>>>
>>>> Do you know of Gecko and WebKit's implementation plans for this?
>>>>
>>>>
>>>> *Web developers*: Positive (https://github.com/w3c/
>>>> IntersectionObserver/issues/431)
>>>>
>>>> *Other signals*:
>>>>
>>>> Ergonomics
>>>>
>>>> N/A
>>>>
>>>>
>>>> Activation
>>>>
>>>> N/A
>>>>
>>>>
>>>> Security
>>>>
>>>> N/A
>>>>
>>>>
>>>> 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
>>>>
>>>> N/A
>>>>
>>>>
>>>> Will this feature be supported on all six Blink platforms (Windows,
>>>> Mac, Linux, Chrome OS, 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://flagsIntersectionObserverScrollMargin
>>>>
>>>> Finch feature nameNone
>>>>
>>>> Non-finch justification
>>>>
>>>> This feature is behind an enabled-by-default flag that can be disabled
>>>> if needed.
>>>>
>>>>
>>>> Requires code in //chrome?False
>>>>
>>>> Tracking bughttps://bugs.chromium.org/p/chromium/issues/detail?id=
>>>> 1469500
>>>>
>>>> Estimated milestonesShipping on desktop119DevTrial on desktop119Shipping
>>>> on Android119DevTrial on Android119Shipping on WebView119
>>>>
>>>> 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/5091020593430528
>>>>
>>>> Links to previous Intent discussionsIntent to prototype:
>>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/
>>>> CAFxahvsWGzF5au6c5%2BfVrh1hOCq_Y0rY0VF_bsmO8VVysg3QTg%40mail.gmail.com
>>>>
>>>> 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/8cc676a6-026d-42ba-9ee9-043684d8b9a8n%40chromium.org
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/8cc676a6-026d-42ba-9ee9-043684d8b9a8n%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/CAOMQ%2Bw9Zg7qciLrEE8r7YZymODXxA%3D%3DjM-Wd1OmvN8pjPcUXGw%40mail.gmail.com.

Reply via email to