- From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
- Date: Fri, 08 Apr 2022 16:15:02 +0000
- To: public-css-archive@w3.org
> In Gecko, if you first `ScrollIntoView - end` (so that the target overflows far to the top/left), then scroll the main window back and click `ScrollIntoView - nearest`, nothing happens because Gecko thinks the target element is already in view. Similarly, `ScrollIntoView - center` also doesn't quite center the visible scroller. > > WebKit seems to do the same thing as Gecko in the `nearest` case but just scrolls to clearly the wrong place in the `center` case which I don't understand. Yeah that seems like a WebKit bug to me too, fwiw. > IMHO the Blink behavior is more intuitive here. That is true, but it feels a bit weird to do some very limited amount of occlusion tracking but not others. I think specifying the simpler thing is better unless there's a need for the more complex thing. > Nice, thanks. I have a similar patch for Blink with a WPT based on my test case in the first message which I should be able to land in the next day or two. Ah, sweet! if you have a WPT ready I don't need to write one :-) Can you cc me on the relevant crbug / review request so I'm aware of when it lands and I don't need to land the Firefox patch without test coverage or forget about it? Thanks! -- GitHub Notification of comment by emilio Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5492#issuecomment-1093053345 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 8 April 2022 16:15:04 UTC