Closed
Bug 904616
Opened 11 years ago
Closed 11 years ago
Correct sizes for hidden preload browsers are never applied
Categories
(Firefox :: Tabbed Browser, defect)
Firefox
Tabbed Browser
Tracking
()
VERIFIED
FIXED
Firefox 26
People
(Reporter: ttaubert, Assigned: ttaubert)
References
Details
(Keywords: regression, verifyme)
Attachments
(2 files)
1.67 KB,
patch
|
jaws
:
review+
|
Details | Diff | Splinter Review |
1.70 KB,
patch
|
ttaubert
:
review+
bajaj
:
approval-mozilla-aurora+
bajaj
:
approval-mozilla-beta+
|
Details | Diff | Splinter Review |
Someone (me) broke the efforts from bug 875257 with bug 881590. Which means that the preloading browsers end up not having the right sizes and we have reflows after docShells have been swapped :( Nominating for tracking because fixing this should be trivial and we certainly don't want a slow tabopen animation.
Comment 2•11 years ago
|
||
Comment on attachment 789596 [details] [diff] [review] Ensure that sizes for preload browsers are applied correctly Review of attachment 789596 [details] [diff] [review]: ----------------------------------------------------------------- Wasn't there supposed to be a test that made sure we didn't regress this?
Attachment #789596 -
Flags: review?(jaws) → review+
Assignee | ||
Comment 3•11 years ago
|
||
(In reply to Jared Wein [:jaws] from comment #2) > Wasn't there supposed to be a test that made sure we didn't regress this? Yeah, that didn't quite land yet...
Assignee | ||
Comment 4•11 years ago
|
||
https://hg.mozilla.org/integration/fx-team/rev/cb1b1f0d16ff
Whiteboard: [fixed-in-fx-team]
Comment 5•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/cb1b1f0d16ff
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [fixed-in-fx-team]
Target Milestone: --- → Firefox 26
Assignee | ||
Comment 6•11 years ago
|
||
[Approval Request Comment] Bug caused by (feature/regressing bug #): bug 881590 User impact if declined: Slow and choppy tabopen animation. Testing completed (on m-c, etc.): Landed on m-c. Risk to taking this patch (and alternatives if risky): Low risk. String or IDL/UUID changes made by this patch: None. Asking for Beta and Aurora approval as this is a really simple fix that vastly improves the tabopen animation, especially on slower machines.
Attachment #790661 -
Flags: review+
Attachment #790661 -
Flags: approval-mozilla-beta?
Attachment #790661 -
Flags: approval-mozilla-aurora?
Comment 7•11 years ago
|
||
(In reply to Tim Taubert [:ttaubert] from comment #6) > Created attachment 790661 [details] [diff] [review] > Ensure that sizes for preload browsers are applied correctly (for beta and > aurora) > > [Approval Request Comment] > Bug caused by (feature/regressing bug #): bug 881590 > User impact if declined: Slow and choppy tabopen animation. > Testing completed (on m-c, etc.): Landed on m-c. > Risk to taking this patch (and alternatives if risky): Low risk. > String or IDL/UUID changes made by this patch: None. > > Asking for Beta and Aurora approval as this is a really simple fix that > vastly improves the tabopen animation, especially on slower machines. Tim, is there a test case for this patch ? Also do we need any help from QA with verification by performing any manual testing for any test cases you may have in mind ?
Assignee | ||
Comment 8•11 years ago
|
||
(In reply to bhavana bajaj [:bajaj] from comment #7) > Tim, is there a test case for this patch ? Also do we need any help from QA > with verification by performing any manual testing for any test cases you > may have in mind ? That's unfortunately bug 876218. I started to work on this a few moons ago but was held up by try issues, iirc. Verifying this is a little tricky, you would need to write some code for it and run that. I could do that, though once it landed on beta/aurora. Or is that maybe not the same as somebody doing it from the QA team? :)
Comment 9•11 years ago
|
||
(In reply to Tim Taubert [:ttaubert] from comment #8) > (In reply to bhavana bajaj [:bajaj] from comment #7) > > Tim, is there a test case for this patch ? Also do we need any help from QA > > with verification by performing any manual testing for any test cases you > > may have in mind ? > > That's unfortunately bug 876218. I started to work on this a few moons ago > but was held up by try issues, iirc. Verifying this is a little tricky, you > would need to write some code for it and run that. I could do that, though > once it landed on beta/aurora. That will be very helpful :) thanks ! >Or is that maybe not the same as somebody > doing it from the QA team? :)
Comment 10•11 years ago
|
||
Comment on attachment 790661 [details] [diff] [review] Ensure that sizes for preload browsers are applied correctly (for beta and aurora) Approving given this is low risk FX25 regression and we are still in early beta's.Tim to help with verification once this lands.
Attachment #790661 -
Flags: approval-mozilla-beta?
Attachment #790661 -
Flags: approval-mozilla-beta+
Attachment #790661 -
Flags: approval-mozilla-aurora?
Attachment #790661 -
Flags: approval-mozilla-aurora+
Assignee | ||
Comment 11•11 years ago
|
||
https://hg.mozilla.org/releases/mozilla-aurora/rev/3b956b39bac4 https://hg.mozilla.org/releases/mozilla-beta/rev/cc28055780cd
Updated•11 years ago
|
status-firefox26:
--- → fixed
Updated•11 years ago
|
Comment 12•11 years ago
|
||
(In reply to Tim Taubert [:ttaubert] from comment #8) > Verifying this is a little tricky, you would need to write some code for it and run that. I could do >that, though once it landed on beta/aurora. Or is that maybe not the same as somebody > doing it from the QA team? :) Hi Tim! Are there any news/updates regarding this? Is there anything QA can help with here? Thanks!
Flags: needinfo?(ttaubert)
Comment 13•11 years ago
|
||
Visually this looks smooth and correct on 24beta10 and Aurora and Nightly builds of 20130913.
Status: RESOLVED → VERIFIED
Assignee | ||
Comment 14•11 years ago
|
||
Confirmed that an old beta version had the wrong sizes. After updating the preload browsers have the correct dimensions.
Flags: needinfo?(ttaubert)
You need to log in
before you can comment on or make changes to this bug.
Description
•