Closed Bug 580621 Opened 14 years ago Closed 14 years ago

Abnormal highlighting of google bottom menu

Categories

(Core :: Layout, defect)

x86
macOS
defect
Not set
minor

Tracking

()

RESOLVED FIXED
Tracking Status
blocking2.0 --- betaN+

People

(Reporter: vladmaniac, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; Windows NT 6.1; rv:2.0b3pre) Gecko/20100721 Minefield/4.0b3pre Build Identifier: Mozilla/5.0 (Windows; Windows NT 6.1; rv:2.0b3pre) Gecko/20100721 Minefield/4.0b3pre When navigating www.google.com and waiting for entire page to load, bottom menu blinks with a black CSS layout. Reproducible: Always Steps to Reproduce: 1.Open Firefox/Minefield 4.0b3pre 2.Navigate www.google.com 3.Wait for page to load completely. 4.Inspect the bottom menu items. If items are not shown, move the cursor anywhere on the page.It should trigger the top menu bar and bottom menu Actual Results: Bottom menu blinks with strange looking black layout element. Expected Results: Bottom menu should load normally. Note: -This is only for MAC OS-X Snow-Leopard -Haven't been able to capture this in screen shot because it happens instantly -It reproduces always, when reloading google page with it's full content
Version: unspecified → Trunk
Blocks: 564991
Status: UNCONFIRMED → NEW
Component: General → Layout
Ever confirmed: true
Product: Firefox → Core
QA Contact: general → layout
blocking2.0: --- → ?
Do not see it anymore in build ID no: 20100722030656. (tested on MAC Snow-Leopard). Could be put to RESOLVED:FIXED and see in further nightlies if it reappears.
Indeed, testing with the following build works correctly: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b3pre) Gecko/20100723 Minefield/4.0b3pre Using http://hourly-archive.localgho.st/hourly-archive2/mozilla-central-macosx/ I tracked it down to these checkins: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=b336127c29d7&tochange=432bca3dd7ba I think 432bca3dd7ba Chris Jones — Bug 573829, part 1: Refactor ThebesLayerBuffer in preparation for its use in the OGL layers backend. r=roc is the one that solved it.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Was that expected to change behavior like this? I guess it's good that it fixed things, though.
blocking2.0: ? → betaN+
Erm, no ... *chin scratch*. Yay?
You need to log in before you can comment on or make changes to this bug.