Respect "apz.disable_for_scroll_linked_effects" pref whether to set HasScrollLinkedEffect::Yes
Categories
(Core :: Panning and Zooming, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox111 | --- | fixed |
People
(Reporter: hiro, Assigned: hiro)
References
Details
Attachments
(1 file)
here in ClipManager::DefineScrollLayers we just use the return value of Document::HasScrollLinkedEffect, but the function doesn't check the pref value at all.
I am guessing this is one of the reasons of bug 1810874 even if the pref value is true.
Assignee | ||
Comment 1•2 years ago
|
||
Updated•2 years ago
|
Comment 3•2 years ago
|
||
(In reply to Hiroyuki Ikezoe (:hiro) from comment #0)
here in ClipManager::DefineScrollLayers we just use the return value of Document::HasScrollLinkedEffect, but the function doesn't check the pref value at all.
I am guessing this is one of the reasons of bug 1810874 even if the pref value is true.
I'm not entirely sure I built Firefox with those changes applied correctly (replacing the files and running "mach run" should be sufficient, right?), but sadly it didn't help with bug 1810874. The behavior with apz.disable_for_scroll_linked_effects=True is still the same.
Comment 4•2 years ago
|
||
(In reply to maciek4231 from comment #3)
(In reply to Hiroyuki Ikezoe (:hiro) from comment #0)
here in ClipManager::DefineScrollLayers we just use the return value of Document::HasScrollLinkedEffect, but the function doesn't check the pref value at all.
I am guessing this is one of the reasons of bug 1810874 even if the pref value is true.
I'm not entirely sure I built Firefox with those changes applied correctly (replacing the files and running "mach run" should be sufficient, right?), but sadly it didn't help with bug 1810874. The behavior with apz.disable_for_scroll_linked_effects=True is still the same.
Sorry, I mistyped, I meant „mach build” of course
Comment 5•2 years ago
|
||
bugherder |
Description
•