Closed Bug 1192918 Opened 9 years ago Closed 9 years ago

[e10s] The page text becomes stretched vertically as the page scrolls

Categories

(Core :: Graphics: Layers, defect)

Unspecified
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1195400
Tracking Status
e10s - ---
firefox41 --- unaffected
firefox42 - disabled
firefox43 + fixed

People

(Reporter: cpeterson, Unassigned)

References

()

Details

(Keywords: regression, Whiteboard: [gfx-noted])

[Tracking Requested - why for this release]:

This bug is a regression in Nightly 42.

@ Matt, I bisected the regression to this mozilla-inbound pushlog, which points to your bug 1180326:

https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=646c99efe919&tochange=69871c00379b

STR:
1. Ensure e10s is enabled!
2. Load https://developers.google.com/youtube/iframe_api_reference
3. Quickly scroll up and down the page.

RESULT:
The page text becomes stretched vertically as the page scrolls.

If you disable e10s, the problem goes away. When I was bisecting this regression, I noticed that this stretched text problem seemed to replace the white APZ "checkerboarding" problem I had on OS X.
This might be bug 1184343.
Updating the bug summary to something far less vague. Chris, please make sure you follow our bug writing guidelines next time: https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines#Writing_a_clear_summary

Thanks.
Summary: [e10s] → [e10s] The page text becomes stretched vertically as the page scrolls
Whiteboard: [gfx-noted]
e10s is going to be disabled in aurora in the next few days, not tracking for 42.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
This is also marked as affecting 42 and 43. The fix in bug 1195400 wasn't uplifted to either branch.  
Is this still affecting 42 or 43?  I don't see it on aurora or beta from OS X 10.10.5.
Flags: needinfo?(cpeterson)
I can't repro on 42 or 43 (though this bug requires e10s, which is not available in 42).
Flags: needinfo?(cpeterson)
You need to log in before you can comment on or make changes to this bug.