Closed Bug 1026271 Opened 10 years ago Closed 10 years ago

Remove the limitation related to the absolutely positioned frames in async scrolling

Categories

(Core :: Graphics, defect, P2)

Product:
Core
Component:
Graphics
Version:
29 Branch
Type:
defect

Tracking

()

Status:
VERIFIED FIXED
Project Flags:
feature-b2g 2.1

People

(Reporter: skamat, Assigned: kats)

References

Details

(Keywords: perf, Whiteboard: [c=handeye p= s= u=][ucid:Graphic20,ft:graphic][2.1-feature-qa+]) 

Remove the limitation related to the absolutely positioned frames in async scrolling

Description: Nested scrolling frames sometimes have to clip an absolutely positioned items they do not contain.  APZ does not properly handle this scenario, which means that we have to fall back into sync scrolling in those cases.
No longer blocks: 1011639, apz-desktop, 1016796
No longer depends on: multi-layer-apz, 1022612
feature-b2g: --- → 2.1
Can you provide a test case for what you're describing? How is this different from bug 967844?
Create dependency to graphic features meta bug used for Forefox OS 2.1.
Blocks: 1016796
Based on the email thread this is just a bug for product management purposes. The implementation is entirely covered by 967844.
Depends on: multi-layer-apz
QA Whiteboard: [2.1-feature-qa+]
Flags: in-moztrap?(npark)
QA Contact: npark
QA Whiteboard: [2.1-feature-qa+]
Whiteboard: [c=handeye p= s= u=][ucid:Graphic20,ft:graphic] → [c=handeye p= s= u=][ucid:Graphic20,ft:graphic][2.1-feature-qa+]
Testing Perspective:
- Use https://bug1011639.bugzilla.mozilla.org/attachment.cgi?id=8424102 to toggle APZC
- Offline discussion with milan to detect APZC scrolling easily, & create more real-life example cases
Testing Perspective:
- Investigate use of nsIDOMWindowUtils.getCompositorAPZTestData()  in bug 961289 to detect APZC, if the test app gives access to nsIDOMWindowUtils.
- Investigate use of apz.printtree pref and counting active APZC in the log (Bug 958596)
Bug 1035917 was the thing that added a message to logcat when we fall back to sync scrolling. I also filed bug 1053992 to add a visual indicator for this.
Depends on: 1053992
This is not actionable (though there may be some action after bug 967844 is resolved), but assigning anyway.
Assignee: nobody → bugmail.mozilla
moztrap link:
https://moztrap.mozilla.org/manage/case/14506/
Flags: in-moztrap?(npark) → in-moztrap+
QA Whiteboard: [2.1-feature-slip+]
All the code for this was handled in bug 967844 which is in 2.1.  Not sure what 2.1-feature-slip+ means, but I'll leave it there, and just close this bug.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
(In reply to Milan Sreckovic [:milan] from comment #9)
> All the code for this was handled in bug 967844 which is in 2.1.  Not sure
> what 2.1-feature-slip+ means, but I'll leave it there, and just close this
> bug.

I was just tagging features that are landing post FL. If bug 967844 did land before merge, then I'll remove the flag.
QA Whiteboard: [2.1-feature-slip+]
QA Whiteboard: [failed-verification]
bug 1064840 has landed now, which means this should be possible to verify now.
QA Whiteboard: [failed-verification] → [needs-verification]
Flags: needinfo?(npark)
Verified with https://bug1011639.bugzilla.mozilla.org/attachment.cgi?id=8424102 and http://people.mozilla.org/~bballo/multi-layer-apz.html  Also other often-used sites/apps scrolled properly without the warning indicator.
Status: RESOLVED → VERIFIED
Flags: needinfo?(npark)
QA Whiteboard: [needs-verification]
You need to log in before you can comment on or make changes to this bug.