Closed Bug 945367 Opened 8 years ago Closed 7 years ago
Need better heuristics at detecting 'root' scrollframe
Gaia apps like the settings app have some fixed position headers thus the primary scroll area is not the root element. We should adjust the heuristics to properly detect the primarily scrollable elements for these.
Yes, I agree. We could probably come up with something, like counting the number of overflow:auto/scroll scrollframes in the page and if there's only one, treat it as always active.
We might want to also check that it covers some 'significant' portion of the page.
With APZ on B2G we now have something similar: nsLayoutUtils::GetOrMaybeCreateDisplayPort (from bug 982141) gives a displayport to the first scrollable frame that's encountered during display list construction.
Depends on: 982141
Is there something we'd like to do here beyond what was already done in bug 982141?
I don't remember if there was anything else to this bug then to bridge the gap until we got multi-APZ. I don't think there is. I think this is WONT FIX since we have a better alternative.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.