Open Bug 2027230 Opened 4 months ago Updated 3 months ago

Testcase generating N chained containers and autoscrolling them blocks the UI (compositor thread) for 8s-10s.

Categories

(Core :: Layout: Scrolling and Overflow, defect, P3)

defect

Tracking

()

People

(Reporter: mayankleoboy1, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Attached file nested Scroll to.html

This is on Windows.

STR:

  1. Open testcase
  2. Click build
  3. Click run
  4. Once the run is complete, click inside the container and try to scroll too.

AR: UI is blocked for multiple seconds. The scrollbars also appear to be weirdly black.
ER: Not so?

https://share.firefox.dev/4s0MDzB, https://share.firefox.dev/4db4WOV

With the "always show scrollbars" in Windows accessibility, the scrollbars atleast appear normally. The page is still slow though.
Chrome is much better here.

Different STR:
Reduce the nesting depth to lets say 10. Increase the iterations to 50000. Click Build and Run
Profile: https://share.firefox.dev/4db515b

Our friend GetScrolledRect. I wonder if it's worth it to try to be smart and avoid all the snapping if the destination scroll coord can't be affected by snapping (ie its definitely in the scroll range).

The severity field is not set for this bug.
:hiro, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(hikezoe.birchill)
Severity: -- → S3
Flags: needinfo?(hikezoe.birchill)
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: