Closed Bug 637224 Opened 14 years ago Closed 7 months ago

Findbar leaves blank space when navigating back while in use

Categories

(Core :: General, defect)

x86
All
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
blocking2.0 --- -

People

(Reporter: mozilla, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: regression)

User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0b12) Gecko/20100101 Firefox/4.0b12 Build Identifier: Mozilla/5.0 (X11; Linux i686; rv:2.0b12) Gecko/20100101 Firefox/4.0b12 The findbar disappears when back (button or keystroke) is pressed, but a blank white space is left and the content area remains the same size it was when the findbar was open. Reproducible: Always Steps to Reproduce: 1. Go to http://www.mesagarden.com/ 2. Click the first link, "Acanthocalycium to Epithelantha" 3. Typeahead find text "davisii" 4. Press backspace/alt-back-arrow, or back button before the findbar closes itself Actual Results: The previous page appears instantly, but the content is smaller than the window and a blank space remains where the findbar was. Expected Results: The previous page appears filling the available content space. I guess the findbar is supposed to disappear now on navigation Although this might appear to be connected to the recent "close findbar on navigation" fix, it happens for me at least as far back as beta 9. Some people have repoted not seeing this, but others have including on Windows 7. It happens for me in safe mode. It doesn't happen on all pages, but it does happen on more than just the one in the example. I think anything that isn't completely cached triggers the white space to disappear.
Confirming and setting to new. I see this on Win7 x64 given the STR by the OP. Tested using latest hourly build on 4.0b13pre cset: http://hg.mozilla.org/mozilla-central/rev/35b6854b0159 Its also been noted that this may have been going on since b9...
Status: UNCONFIRMED → NEW
Ever confirmed: true
Regresson window: Works: http://hg.mozilla.org/mozilla-central/rev/e7e7a4fe417c Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a5pre) Gecko/20100421 Minefield/3.7a5pre ID:20100421065127 Fails: http://hg.mozilla.org/mozilla-central/rev/8c551a93eedd Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a5pre) Gecko/20100421 Minefield/3.7a5pre ID:20100421084103 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=e7e7a4fe417c&tochange=8c551a93eedd
Version: unspecified → Trunk
In local build, build from f3abfe490d7f :fails build from e7e7a4fe417c :works Regressed by: f3abfe490d7f Neil Deakin — Bug 418521, improve the way focus indicators are displayed to correlate better with system behaviour, add -moz-focusring property to apply only when focus rings should be drawn, r=dao,jmathies,dbaron sr=neil
Product: Firefox → Core
QA Contact: general → general
This problem also happens on http://www.mozilla.com/en-US/mobile/ So, this problem is not a special. and should be fixed. Steps to Reproduce: 1. Go to http://www.mozilla.com/en-US/mobile/ 2.Learn More » in the paragraph "Your Life In Sync" 3. Typeahead find (/) 4. Press backspace/alt-back-arrow, or back button before the findbar closes
After landing Bug 628179. This problem can happen _frequently_. Steps to Reproduce: 1. Go to http://www.google.com/ 2. Search Firefox 3. Click first search result link 4. Open Findbar Ctrl+F 5. Navigation Back (the Findbar will hide automatically)
Blocks: 628179
blocking2.0: --- → ?
I wonder if we get an assertions when this happens in a debug build.
I am unable to repo this on 3.6.13 on WinXP SP3. So, is this Win7/Vista only or something with Hardware Accel ?
Jim, this bug is 4.0-specific. It's not present in 3.6.x.
Blocking until we back out bug 628179 which made this more apparent. Once that's backed out, we'll unblock on this.
blocking2.0: ? → final+
Whiteboard: [hardblocker]
Whiteboard: [hardblocker] → [hardblocker][will be fixed by backout of bug 628179]
Unblocking now that bug 628179 is backed out.
blocking2.0: final+ → -
Whiteboard: [hardblocker][will be fixed by backout of bug 628179]
In latest nightly, a findbar invoked with ctrl-F remains even after navigation. So no blank space appears when navigating back in any case I've tested. A findbar invoked with typeahead find still disappears on navigation (it always did, right, not just on timeout?) so the blank space can still appear in those cases. I never noticed this prior to the recent changes although going back now it is easy to reproduce.
Severity: minor → S4

This seems to work in today's nightly, and I assume it is not worth understanding what fixed it.

Status: NEW → RESOLVED
Closed: 7 months ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.