Zooming on Jira bugreports causes unresponsive / cut off content on buttom
Categories
(Core :: Panning and Zooming, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | wontfix |
firefox75 | --- | unaffected |
People
(Reporter: linuxhippy, Unassigned)
References
()
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:75.0) Gecko/20100101 Firefox/75.0
Steps to reproduce:
- Opend a JIRA bug report with firefox for Andoird
- scrolled to bottom and zommed a bit
Actual results:
the content seems to be cut-off, there is a dead area on the bottom of the page where no content is shown and scroll-input is ignored: https://youtu.be/noH_-IATW7Y
Expected results:
the page should behave the same as with google chrome for android.
the full content should be shown, zooming and scrolling should work as expected.
Reporter | ||
Comment 1•5 years ago
|
||
one of the URLs where this behavour can be observed: https://bugs.openjdk.java.net/browse/JDK-8238246
Hi Diana, can you check if this also happens in Fenix?
Hi, yes of course, I managed to reproduce the issue with Google Pixel 3a (Android 9) and Sony Xperia Z5 (Android 7.0.0) on Firefox Release 68.5.0 and Firefox Beta 68.6b2.
On Firefox Preview Nightly 200219 (Build #20500606) GV: 75.0a1-20200218093736 the issue does not reproduce, fortunately.
Please view video.
I will mark the ticket as NEW for fennec.
Updated•5 years ago
|
Comment 4•5 years ago
|
||
Comment 3 sounds like it happens on Fennec but not Fenix. So this should be WONTFIX?
Comment 5•5 years ago
|
||
Possibly related to bug 1478690, since it looks like the displayport for the subframe is not placed correctly after zooming in on the root frame.
Comment 6•5 years ago
|
||
(In reply to Kartikaya Gupta (email:kats@mozilla.com) from comment #4)
Comment 3 sounds like it happens on Fennec but not Fenix. So this should be WONTFIX?
We sometimes fix Fennec bugs, or uplift existing fixes to ESR, though admittedly that's been happening less often as time has gone on.
Comment 7•5 years ago
|
||
Based on the symptoms, I'd say this is likely the same issue as bug 1546222, which is a dupe of bug 1565512, which was wontfixed for 68esr.
Comment 8•5 years ago
|
||
(In reply to Botond Ballo [:botond] from comment #7)
Based on the symptoms, I'd say this is likely the same issue as bug 1546222, which is a dupe of bug 1565512, which was wontfixed for 68esr.
This theory seems to be wrong.
Mozregression in fact points to bug 1514429, which wasn't considered for ESR uplift (and probably shouldn't be given its regression risk).
Updated•5 years ago
|
Updated•5 years ago
|
Description
•