[Webkit-unassigned] [Bug 237747] Web Inspector: REGRESSION(?): Styles: creating a new property scrolls the input to the top of the panel

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=237747

Razvan Caliman <rcaliman at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rcaliman at apple.com

--- Comment #2 from Razvan Caliman <rcaliman at apple.com> ---
Created attachment 454881

  --> https://bugs.webkit.org/attachment.cgi?id=454881&action=review

Recording of bug

There’s an ever easier way to test:
- Inspect the body element on webkit.org
- In the Styles panel, click to add a new CSS declaration to Style Attribute section. 

The bug manifests by scrolling the Styles panel down to the CSS property name input field.
See attached video recording.
—- 

Autospade says:

Works: Internal ddfb413d76c9 - OpenSource r290769
Fails: Internal ddfb413d76c9 - OpenSource r290770
https://trac.webkit.org/changeset/290770

Bug 237189 - Treat empty intersection correctly in RenderLayer::getRectToExpose
https://bugs.webkit.org/show_bug.cgi?id=237189

But my hunch is that it’s actually caused by another patch:
Bug 42593 - element.scrollIntoView() sometimes doesn’t scroll
https://bugs.webkit.org/show_bug.cgi?id=42593

That patch also relies on changes to RenderLayer.cpp to determine what counts as visible.
So I think our regression point compounded with the changes to how `Element.scrollIntoView()` works.

The Changelog is kind of telling:

> For some operations which scroll to a rectangle, if an object is more than
> 32 pixels onscreen, it’s not considered onscreen. This was originally used
> to prevent unnecessary scrolling while tabbing through form fields, but is
> no longer used for that in the majority of cases. Instead, the behavior affects
> the calls to Element.focus(), Element.scrollIntoView(), and navigations to
> anchor elements.

I’m not yet sure how to approach this. Ideas are very welcome. 

cc @Nikita Vasilyev who filed the original bug about `Element.scrollIntoView()`

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220316/90181337/attachment.htm>