Uncontrollable page scrolling after middle mouse click on <object>-embedded svg element
Categories
(Firefox :: General, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox72 | --- | unaffected |
firefox73 | + | fixed |
firefox74 | + | fixed |
People
(Reporter: jaso35, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
851 bytes,
text/html
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
Open the attached test-case which contains an <object>-embedded svg element in Firefox.
Click on the blue area with the middle mouse button and try to scroll a bit.
Terminate scrolling by clicking with the middle mouse button in the blue area again.
This behaviour was noticed with the embedded svg flowcharts contained in https://www.onkopedia-guidelines.info/en/onkopedia/guidelines/chronic-lymphocytic-leukemia-cll/@@guideline/html/index.html
Actual results:
The scrolling behaviour becomes uncontrollable now. By just moving your mouse up and down, the page scrolls. Using the scroll bar will make the page scroll by itself back to the starting position. This behaviour can only be stopped by reloading the page.
Expected results:
Scrolling should stop after the second middle mouse click.
Reporter | ||
Comment 1•6 years ago
|
||
This is the mentioned testcase.
Reporter | ||
Updated•6 years ago
|
![]() |
||
Comment 2•6 years ago
|
||
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=bba57a78314a41dd3a855def379afd401d5fd7b0&tochange=0450c6ad5b8502e78973fe9462c0cb6a37f6b40c
(I can't bisect anymore due to browser crash)
Regressed by: 2c56e1bfbff982873521af50eb62c7bf8f300cf1 Alexander Surkov — Bug 1597765 - support auto scroll in out of process frames
Updated•6 years ago
|
Reporter | ||
Comment 3•6 years ago
|
||
I managed to bisect it a bit further. Seems like you got it right.
Updated•6 years ago
|
Comment 4•6 years ago
|
||
can't reproduce it on Nightly, I suspect bug 1606108 fixed it
Updated•6 years ago
|
Updated•6 years ago
|
Description
•