Closed
Bug 1339925
Opened 7 years ago
Closed 1 year ago
Text in scrollable frame is rendered outside the scrollable frame (not clipped properly) when displayport expires
Categories
(Core :: Web Painting, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox51 | --- | unaffected |
firefox52 | --- | unaffected |
firefox-esr52 | --- | unaffected |
firefox-esr60 | --- | wontfix |
firefox53 | --- | unaffected |
firefox54 | --- | wontfix |
firefox55 | --- | wontfix |
firefox56 | --- | wontfix |
firefox57 | --- | wontfix |
firefox58 | --- | wontfix |
firefox59 | --- | wontfix |
firefox60 | --- | wontfix |
firefox61 | --- | wontfix |
firefox62 | --- | fix-optional |
People
(Reporter: kats, Assigned: mstange)
References
(Blocks 2 open bugs, )
Details
(Keywords: regression)
Attachments
(2 files)
Latest Fennec Nightly on a Z3C with CM 12.1 (~Android 5.1.1). Load [1], scroll the attachment down to the bottom and wait 15 seconds for the displayport to expire. Expected: no visible change. Actual: text from the attachment is drawn outside the scrollable subframe. See attached screenshot. [1] https://bugzilla.mozilla.org/attachment.cgi?id=8837566&action=edit
Reporter | ||
Comment 1•7 years ago
|
||
I don't see this in 52 beta or 53 aurora, so probably a recent regression. I'll mozregress it.
Reporter | ||
Comment 2•7 years ago
|
||
mozregression narrowed it down to this: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=f985243bb630b2c78cd57731c8d8ab191aa09527&tochange=bf15d4078c2a6db7df37ab466d28a1e075c9eb4d It was unable to find builds in taskcluster so couldn't bisect any further. However Markus' clipping patches are in that range and are a likely culprit.
Blocks: 1298218
status-firefox51:
--- → unaffected
Updated•7 years ago
|
Flags: needinfo?(mstange)
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → mstange
Status: NEW → ASSIGNED
Updated•7 years ago
|
status-firefox55:
--- → affected
Updated•7 years ago
|
status-firefox-esr52:
--- → unaffected
Updated•7 years ago
|
Flags: needinfo?(milan)
Updated•7 years ago
|
Flags: needinfo?(mstange)
Flags: needinfo?(milan)
Markus, is this something that looks like it'd fit in your 55 schedule? Or, can you provide guidance for somebody else to fix it?
Flags: needinfo?(mstange)
Assignee | ||
Comment 4•7 years ago
|
||
Stuff outside the iframe: asr(<0x85e7df10>) agr=0x85e7dca0 clipChain() Stuff inside the iframe: asr(<0x8e57fdc8>, <0x85e7df10>) agr=0x85e7dca0 clipChain(<1290,12164,53608,24000> [0x85e7df10]) So in terms of asr, the contents are still layerized, but in terms of AGR they're not. There's code in FrameLayerBuilder that is supposed to detect this discrepancy and apply any scroll clips that will not be set on the layer to the display items. It looks like that's not working properly here.
Comment 5•7 years ago
|
||
Unsure if we think this is important enough to fix for 57, or if it can wait.
status-firefox56:
--- → wontfix
status-firefox57:
--- → affected
Updated•7 years ago
|
Priority: -- → P3
Reporter | ||
Comment 7•6 years ago
|
||
Yes, still seeing this on current Nightly. Android 8.0, Sony Xperia XZ1 compact.
Flags: needinfo?(bugmail)
Updated•6 years ago
|
status-firefox58:
--- → wontfix
status-firefox59:
--- → fix-optional
status-firefox60:
--- → affected
Updated•6 years ago
|
status-firefox61:
--- → wontfix
status-firefox62:
--- → fix-optional
status-firefox-esr60:
--- → wontfix
Comment 8•6 years ago
|
||
This is fixed by the patch in bug 1486695.
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Comment 9•6 years ago
|
||
Unfortunately, the version of the patch in bug 1486695 that actually landed, does not fix this. The previous version of the patch unintentionally tried to disable container scrolling for iframe RSFs; presumably it was that change that fixed this bug. However, that version was failing many tests. We do eventually want to disable container scrolling across the board, and that should fix this bug, but that's a larger change.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Updated•2 years ago
|
Severity: normal → S3
Assignee | ||
Comment 10•1 year ago
|
||
This was probably fixed by WebRender.
Status: REOPENED → RESOLVED
Closed: 6 years ago → 1 year ago
Flags: needinfo?(mstange.moz)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•