Closed Bug 1052182 Opened 11 years ago Closed 11 years ago

Google search box shrunk in recent Nightly builds

Categories

(Core :: Layout, defect)

34 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1051511
Tracking Status
firefox33 --- unaffected
firefox34 --- affected

People

(Reporter: u279076, Unassigned)

Details

(Keywords: regression)

Attachments

(1 file)

[Tracking Requested - why for this release]: I updated my Nightly from about a week ago and noticed the search box on Google websites has shrunk in horizontal size. I tried in Chrome and the search box is still the original size. I downgraded Nightly to July 23rd and the search box reverted to the normal size. As such I think there's a recent regression. I'll try to track down a regression window. To reproduce it yourself, simply load www.google.com/finance in the latest Nightly and Chrome to compare. Attached is a screenshot which compares today's Nightly (top) to the July 23rd Nightly (bottom).
Last good revision: 18f408a5984e (2014-08-08) First bad revision: 83f519eb1a3a (2014-08-09) Pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=18f408a5984e&tochange=83f519eb1a3a
Last good revision: 3ac1b309271d First bad revision: aece7f9f944c Pushlog: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=3ac1b309271d&tochange=aece7f9f944c Looks like this is caused by bug 1032922.
Blocks: 1032922
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
(I was going to cancel the tracking flag, but I'm not sure how to manage tracking flags on tech evang bugs. This could arguably be considered "tracking+" in the sense that, if Google didn't fix their CSS, we'd definitely want to back out bug 1032922 rather than ship a final or beta release with this bug. It probably won't matter since it sounds like they're already looking into it on their end, per bug 1052182 comment 21. But ashughes, feel free to transfer the tracking request or just cancel it, as you see fit.) (and if you want a local workaround, you can use my stylish user-style from bug 1051511 comment 17)
Flags: needinfo?(anthony.s.hughes)
(In reply to Daniel Holbert [:dholbert] from comment #4) > ashughes, feel free to transfer the tracking request or just cancel it, as you see fit.) I'll leave that to Release Management. I'm not sure what the normal process is here.
Flags: needinfo?(anthony.s.hughes) → needinfo?(release-mgmt)
(In reply to Daniel Holbert [:dholbert] from comment #4) > (I was going to cancel the tracking flag, but I'm not sure how to manage > tracking flags on tech evang bugs. This could arguably be considered > "tracking+" in the sense that, if Google didn't fix their CSS, we'd > definitely want to back out bug 1032922 rather than ship a final or beta > release with this bug. > > It probably won't matter since it sounds like they're already looking into > it on their end, per bug 1052182 comment 21. But ashughes, feel free to > transfer the tracking request or just cancel it, as you see fit.) > > (and if you want a local workaround, you can use my stylish user-style from > bug 1051511 comment 17) If you no longer feel a bug should be nominated for tracking feel free to unflag it in the future.
Flags: needinfo?(release-mgmt)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: