Open
Bug 725983
Opened 13 years ago
Updated 2 years ago
Over-invalidation in former gaia contacts screen
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
NEW
People
(Reporter: cjones, Unassigned)
References
Details
Attachments
(2 files, 1 obsolete file)
STR
(1) Load the attached test case.
(2) Click the middle button at the bottom of the page.
(3) Scroll up and down
The entire scrollable area is repainted on every scroll. For some reason we're not activating the scrolling layer, so we're not hitting the buffer rotation optimization.
I see something slightly different on device, where part of the static view (surrounding the scrollable area), above the scrollable view, is being invalidated.
The test is single-page but not reduced yet.
|
Reporter | |
Comment 1•13 years ago
|
||
Some useful reductions to be done here
- remove the "dialer" and "favorites" screens
- make the contacts part of the page statically, don't dynamically load them. Leave enough contacts that the inner div overflows and is scrollable.
- cut out support for popping up the detailed contacts screen
- after load, have something drive an animation of the scrollTo inner div, slowly, for 10 seconds or so
- and of course, remove irrelevant elements and CSS
|
|
Reporter | |
Comment 2•13 years ago
|
||
See the test. Important part is
/* Without the border, we don't invalidate the entire window. */
border: 1px #333333 solid;
If I remove the container div and try to set up the <body> the same way, I don't see the invalidation bug whether or not the border is present.
Attachment #596039 -
Attachment is obsolete: true
|
||
Comment 3•13 years ago
|
||
A test showing that we invalidate *outside*. Maybe unrelated though, since
it occurs also without a border.
|
|
||
Comment 4•13 years ago
|
||
Chris, in case you're interested in a workaround, changing the border to outline
and then making room for it with "body { -moz-box-sizing:border-box; padding:1px; }"
seems to work for me.
(In reply to Chris Jones [:cjones] [:warhammer] from comment #2)
> Created attachment 596439 [details]
> small test case
What are the steps to reproduce here?
|
|
Reporter | |
Comment 6•13 years ago
|
||
Turn on paint flashing, load the test, scroll it.
WFM with D3D10.
|
|
Reporter | |
Comment 8•13 years ago
|
||
Hm, I don't see excessive invalidation in latest Nightly, but I in my build with "fixes" for other bugs applied. Investigating.
|
|
Reporter | |
Comment 9•13 years ago
|
||
OK, test case over-invalidates in debug build from same cset as nightly ....
|
|
Reporter | |
Comment 10•13 years ago
|
||
Getting an ICE building opt on tip. Fabulous.
|
||
Updated•12 years ago
|
Blocks: b2g-product-phone
|
|
||
Updated•12 years ago
|
No longer blocks: b2g-demo-phone
|
|
Reporter | |
Comment 11•12 years ago
|
||
DLBI didn't fix this.
Summary: Over-invalidation in gaia contacts screen → Over-invalidation in forme gaia contacts screen
Assignee: nobody → matt.woodrow
|
|
Reporter | |
Comment 12•12 years ago
|
||
To be clear, in this and the other invalidation bug, I was looking at the attached testcases in desktop FF. Not the year+ old gaia apps on phone ;).
Summary: Over-invalidation in forme gaia contacts screen → Over-invalidation in former gaia contacts screen
|
||
Comment 13•3 years ago
|
||
The bug assignee didn't login in Bugzilla in the last 7 months, so the assignee is being reset.
Assignee: matt.woodrow → nobody
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•