Closed
Bug 807934
Opened 13 years ago
Closed 13 years ago
background image not invalidating on browser resize
Categories
(Core :: Layout, defect)
Tracking
()
VERIFIED
FIXED
Tracking | Status | |
---|---|---|
firefox17 | --- | unaffected |
firefox18 | + | verified |
firefox19 | + | verified |
People
(Reporter: brunis, Assigned: roc)
References
()
Details
(Keywords: regression)
Attachments
(3 files)
4.38 KB,
text/html
|
Details | |
215 bytes,
text/html
|
Details | |
3.44 KB,
patch
|
Details | Diff | Splinter Review |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/19.0 Firefox/19.0
Build ID: 20121101180809
Steps to reproduce:
go here: http://www.computercity.dk/default.aspx
resize browser horizontally (either way)
Actual results:
Background image not being invalidated, so it stays where it was initially rendered
Expected results:
Background image should invalidate and display correctly
Blocks: dlbi
Status: UNCONFIRMED → NEW
Component: Untriaged → Layout
Ever confirmed: true
Product: Firefox → Core
Version: 19 Branch → Trunk
Not a proper DLBI bug, it's more recent. Surely a regression in a fix about DLBI bug.
m-c
good=2012-10-26
bad=2012-10-27
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=5ecff3e46ed5&tochange=f9acc2e4d4e3
No longer blocks: dlbi
tracking-firefox19:
--- → ?
Keywords: regression,
regressionwindow-wanted
Version: Trunk → 19 Branch
![]() |
||
Comment 2•13 years ago
|
||
![]() |
||
Comment 3•13 years ago
|
||
Regression window(m-i)
Good:
http://hg.mozilla.org/integration/mozilla-inbound/rev/71e97a4400ea
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/19.0 Firefox/19.0 ID:20121025182629
Bad:
http://hg.mozilla.org/integration/mozilla-inbound/rev/8a29f06470f7
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/19.0 Firefox/19.0 ID:20121025184029
Pushlog:
http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=71e97a4400ea&tochange=8a29f06470f7
Suspected: Bug 801488
Blocks: 801488
Keywords: regressionwindow-wanted
Assignee | ||
Comment 4•13 years ago
|
||
Must be the patch that removed Redraw() from nsStackLayout.
Assignee: nobody → roc
Assignee | ||
Comment 5•13 years ago
|
||
Try resizing the window with this testcase open.
I'm pretty sure this dates back to DLBI and the patch in bug 801488 only exposed it because we no-longer force-redraw the entire window on resize.
Assignee | ||
Comment 6•13 years ago
|
||
http://dxr.mozilla.org/mozilla-central/layout/base/nsDisplayList.cpp.html#l2095
// This is incorrect, We definitely need to check more things here.
No kidding!
Assignee | ||
Updated•13 years ago
|
Assignee | ||
Comment 7•13 years ago
|
||
It seems to me that the right way to fix this might be to make nsDisplayBackgroundGeometry store (instead of mPadding/mContent) explicit background positioning area and background painting area. What do you think Matt? I need to sleep on it :-).
Assignee | ||
Comment 8•13 years ago
|
||
Comment 9•13 years ago
|
||
I think we just want bug 798964 to be finished, which should implicitly includes those as the bounds of the display items. Was stuck on some bizarre android-specific failures though.
Comment 7 would probably work too though, I think I guessed with using mPadding/mContent.
Assignee | ||
Comment 10•13 years ago
|
||
(In reply to Matt Woodrow (:mattwoodrow) from comment #9)
> I think we just want bug 798964 to be finished, which should implicitly
> includes those as the bounds of the display items.
It would fix this bug, yes, but somewhat by accident, since the display item bounds would be the image bounds and the image bounds would move. I think we could have other situations where the background painting area doesn't change but the background positioning area does change, so bug 798964 wouldn't necessarily invalidate in that case. Also converting to painting area/positioning area would be more elegant.
Also, we need to fix this bug for FF18 release. Are you planning to fix bug 798964 for that?
Comment 11•13 years ago
|
||
Fair call, no I don't think we should be uplifting bug 798964 to aurora.
Updated•13 years ago
|
status-firefox17:
--- → unaffected
status-firefox18:
--- → affected
status-firefox19:
--- → affected
tracking-firefox18:
--- → +
Assignee | ||
Comment 12•13 years ago
|
||
I ended up going on a bit of a rampage. I'll probably need to come up with a different fix for Aurora...
https://tbpl.mozilla.org/?tree=Try&rev=38ac9803cf90
Assignee | ||
Comment 13•13 years ago
|
||
The reftests in that push are green.
Assignee | ||
Comment 14•13 years ago
|
||
This is the really simple fix for this testcase. It should be good enough.
Attachment #680208 -
Flags: review?(matt.woodrow)
Assignee | ||
Comment 15•13 years ago
|
||
I'm moving my major changes to bug 810470.
Updated•13 years ago
|
Attachment #680208 -
Flags: review?(matt.woodrow)
Comment 16•13 years ago
|
||
Fixed by bug 810470.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•13 years ago
|
Comment 17•13 years ago
|
||
Verified Fixed for FF 18.b4 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0 (20121212073002)
Resizing browser works as expected.
Updated•13 years ago
|
QA Contact: mariomihai22
Updated•13 years ago
|
QA Contact: mariomihai22
Comment 18•13 years ago
|
||
Verified Fixed on FF 19.b1 on Windows 7x64 too.
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101 Firefox/19.0(20130109111322)
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•