864768 - Ctrl+F does nothing on "New Tab" page

Status: RESOLVED DUPLICATE of bug 866400

(Firefox :: General, defect)

Description

[ojab]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20130423 Firefox/23.0
Build ID: 20130423030935

Steps to reproduce:

1a. Open "New Tab"
2a. Ctrl+F (open find bar)

1b. Ctrl+F (open find bar)
2b. Open "New Tab"
3b. Ctrl+F (focus on find bar)




Actual results:

nothing


Expected results:

a. Opened and focused find bad
b. Focus on find bar

Comment 1

[Liz Henry (:lizzard) (relman/hg->git project)]

I was able to reproduce this in Nightly (23.0a1).

Comment 2

[Manuela Muntean [Away]]

Ubuntu 12.10 32-bit machine

Not reproducible on the latest Beta - build ID: 20130423212553
Reproducible on the latest Aurora - build ID: 20130423004014
Reproducible on the latest Nightly - build ID: 	20130423030935


Note:
This issue is a regression, because it doesn't reproduce with Firefox 4.0. I will come back with a regression window as soon as possible.

Comment 3

[Manuela Muntean [Away]]

Last good nightly: 2013-03-27
First bad nightly: 2013-03-28

Pushlog:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=178a4a770bb1&tochange=962f5293f87f

Comment 4

[:Gavin Sharp [email: [e-mail]]]

The new tab page has had "disablefastfind" attribute on it for a long time (since at least bug 736476), so as far as I can tell this is INVALID.

I don't understand why this behavior would have changed more recently in the range in comment 3, though.

Comment 5

[Tim Taubert [:ttaubert] (inactive)]

(In reply to :Gavin Sharp (use [e-mail] for email) from comment #4)
> The new tab page has had "disablefastfind" attribute on it for a long time
> (since at least bug 736476), so as far as I can tell this is INVALID.

Yes, afaik disablefastfind was there since we introduced about:newtab. I think we could revisit this decision, though. I can't remember why exactly I added this but I think this was not a requirement from UX.

Comment 7

[:Gavin Sharp [email: [e-mail]]]

(In reply to :Gavin Sharp (use [e-mail] for email) from comment #4)
> I don't understand why this behavior would have changed more recently in the
> range in comment 3, though.

I still would like to understand this, if anyone has any ideas!

Comment 8

[Tim Taubert [:ttaubert] (inactive)]

(In reply to Manuela Muntean [:Manuela] [QA] from comment #3)
> Last good nightly: 2013-03-27
> First bad nightly: 2013-03-28
> 
> Pushlog:
> http://hg.mozilla.org/mozilla-central/
> pushloghtml?fromchange=178a4a770bb1&tochange=962f5293f87f

I bisected - it's the cause of bug 855273:
https://hg.mozilla.org/mozilla-central/rev/1a59fb1ccd6b

Not sure what exactly caused it and what the requirements for (not) showing the find bar are.