LGTM1

On Mon, Dec 16, 2024 at 2:10 PM David Awogbemila <awogbem...@chromium.org>
wrote:

> The CSS working group resolved
> <https://github.com/w3c/csswg-drafts/issues/11173#issuecomment-2536659205> to
> make some changes based on TAG feedback. The property is now named
> "scroll-initial-target" and its keywords are "none" and "nearest." I've
> updated the chromestatus page
> <https://chromestatus.com/feature/6276178888097792>.
>
> On Wed, Nov 20, 2024 at 3:35 PM David Awogbemila <awogbem...@chromium.org>
> wrote:
>
>> Wanted to provide a quick update on this feature:
>> TAG feedback
>> <https://github.com/w3ctag/design-reviews/issues/1011#issuecomment-2471818871>
>> suggested considering a different name for the property. I've filed an
>> issue <https://github.com/w3c/csswg-drafts/issues/11173> with the CSS
>> working group to come up with a new name.
>>
>> On Wed, Nov 6, 2024 at 11:39 AM David Awogbemila <awogbem...@chromium.org>
>> wrote:
>>
>>>
>>>
>>> On Wed, Nov 6, 2024 at 9:01 AM Mike Taylor <miketa...@chromium.org>
>>> wrote:
>>>
>>>> On 11/5/24 5:17 PM, David Awogbemila wrote:
>>>>
>>>> Contact emails awogbem...@chromium.org, arg...@chromium.org
>>>>
>>>> Explainer
>>>> https://github.com/DavMila/explainer-scroll-start-target?tab=readme-ov-file
>>>>
>>>> Specification
>>>> https://drafts.csswg.org/css-scroll-snap-2/#scroll-start-target
>>>>
>>>> Summary
>>>>
>>>> scroll-start-target is a CSS property that allows authors indicate that
>>>> an element should be scrolled into view when its scroll container is first
>>>> displayed on a page. scroll-start-target is a CSS property that gives web
>>>> authors the ability to have a scroll container scrolled to its child (the
>>>> target) when the container first shows up on the page. Similar to instantly
>>>> scrolling to a URL fragment identifier when a page loads, this property
>>>> provides an easier and more reliable way to achieve non-(0,0) default
>>>> scroll position instead of other methods like JavaScript's scrollIntoView
>>>> or animations on scroll-snap-align.
>>>>
>>>>
>>>> Blink component Blink>Scroll
>>>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EScroll>
>>>>
>>>> TAG review https://github.com/w3ctag/design-reviews/issues/1011
>>>>
>>>> TAG review status Pending
>>>>
>>>> Risks
>>>>
>>>>
>>>> Interoperability and Compatibility
>>>>
>>>> None
>>>>
>>>>
>>>> *Gecko*: No signal (
>>>> https://github.com/mozilla/standards-positions/issues/1107)
>>>>
>>>> *WebKit*: No signal (
>>>> https://github.com/WebKit/standards-positions/issues/423)
>>>>
>>>> *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)? No
>>>>
>>>> Can you say more?
>>>>
>>>
>>> Apologies, I somehow forgot to flip this bit. This should have said Yes.
>>> I've updated the chromestatus page.
>>>
>>>>
>>>> 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-scroll-snap-2/scroll-start-target?label=master&label=experimental&aligned
>>>>
>>>>
>>>> Flag name on about://flags None
>>>>
>>>> Finch feature name CSSScrollStartTarget
>>>>
>>>> Requires code in //chrome? False
>>>>
>>>> Tracking bug https://crbug.com/40909052
>>>>
>>>> Sample links
>>>> https://davmila.github.io/demo-scroll-start-target/drones/index.html
>>>> https://davmila.github.io/demo-scroll-start-target/gallery/index.html
>>>> https://davmila.github.io/demo-scroll-start-target/todo/index.html
>>>>
>>>> Estimated milestones
>>>>
>>>> No milestones specified
>>>>
>>>>
>>>> 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/6276178888097792?gate=6225358956003328
>>>>
>>>> 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 visit
>>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAA6pwF6K1mqXxgQS6%2BYN7NNAd%2BNbSeDk8mkv_h7bph0oeZpf3Q%40mail.gmail.com
>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAA6pwF6K1mqXxgQS6%2BYN7NNAd%2BNbSeDk8mkv_h7bph0oeZpf3Q%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 visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAA6pwF7xF7orFBZJRraQAbY69O4k16pQddU%2BJjpQut5EEe2Qpw%40mail.gmail.com
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAA6pwF7xF7orFBZJRraQAbY69O4k16pQddU%2BJjpQut5EEe2Qpw%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 visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw8QnUqUr%3DGLX6noLrXWp%3D7SnjrHVFY3wsWuCL16jZv4FQ%40mail.gmail.com.

Reply via email to