Closed
Bug 1396762
Opened 7 years ago
Closed 5 months ago
SVG pages: Video is not displayed/truncated when zoom is increased (150%) and page is scrolled down/up
Categories
(Core :: Layout, defect, P3)
Tracking
()
People
(Reporter: roxana.leitan, Unassigned)
References
Details
(Keywords: regression)
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:56.0) Gecko/20100101 Firefox/56.0
Build ID: 20170831165232
[Affected versions]:
Beta 56.0b8, Nightly 57.0a1
[Affected platforms]:
Mac OS X 10.12, Windows 10 x64
1.Launch Firefox 56.0b8 with new profile
2.Go to http://www.playmag.fr/heroesoftomorrow
3.Set zoom page at 150%
4.Scroll down
5.Scroll up to top of page
[Expected result]:
Video is still playing
[Actual result]:
Video is missing/truncated
Do we know if this is a regression from 55?
Using the Mozregression tool, I have found a regression window:
Last good revision: 3a67958e318a8603588e8403fc1926a978e86633
First bad revision: 41d66b1327ace3c314d196154381713ed4188299
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=3a67958e318a8603588e8403fc1926a978e86633&tochange=41d66b1327ace3c314d196154381713ed4188299
Updated•7 years ago
|
Comment 3•7 years ago
|
||
Too late for 56 but we could still take a patch for 57.
Updated•7 years ago
|
![]() |
||
Updated•7 years ago
|
Comment 4•7 years ago
|
||
Maire, should we try to find a new owner for this one?
Flags: needinfo?(mreavy)
Comment 5•7 years ago
|
||
I don't have a new owner for this at this point. I also am moving this to a P3. It's officially a regression, but it's not a critical use case, and we've been living with it since 52. The biggest impact may be to a11y use cases. If someone wants to advocate for this one, please chime in.
Flags: needinfo?(mreavy)
Priority: P2 → P3
Updated•2 years ago
|
Severity: normal → S3
Comment 6•5 months ago
|
||
Closing this as WFM as it is no longer reproducible with our latest nightly build 132.0a1 (2024-09-27) using Win 10 and macOS 11.
Status: NEW → RESOLVED
Closed: 5 months ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•