Closed
Bug 1280354
Opened 8 years ago
Closed 8 years ago
New page search regression, cannot use link with "Enter"
Categories
(Toolkit :: Find Toolbar, defect)
Tracking
()
VERIFIED
FIXED
Tracking | Status | |
---|---|---|
firefox49 | --- | unaffected |
firefox50 | --- | unaffected |
People
(Reporter: petcuandrei, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: nightly-community, regression)
Attachments
(2 files)
User Agent: Mozilla/5.0 (Android 5.1.1; Mobile; rv:49.0) Gecko/49.0 Firefox/49.0
Build ID: 20160614004007
Steps to reproduce:
1) open a page
2) Ctrl+F "some link"
3) Hit Enter and jump from one search suggestion to another
4) stop on one search result and click Esc and then Enter
Actual results:
It does not "click" on the page as it used to a few days ago. This changed with the new search highlight.
Expected results:
It should "click" on the selected link.
Reporter | ||
Updated•8 years ago
|
OS: Unspecified → All
Hardware: Unspecified → x86_64
Version: 49 Branch → 50 Branch
Comment 1•8 years ago
|
||
STR
1. Open testcase
2. Ctrl+F to open Findbar
3. Type BMO
4. Hit [ESC] key to close Findbar
5. Hit [ENTER] key
Actual Results:
Findbar open
Expected Results:
Navigate to https://bugzilla.mozilla.org/
Updated•8 years ago
|
Blocks: 384458
Status: UNCONFIRMED → NEW
status-firefox50:
--- → affected
Component: Untriaged → Find Toolbar
Ever confirmed: true
Product: Firefox → Toolkit
Comment 2•8 years ago
|
||
The test case behaves as expected for me, Enter activates the link.
I tested on both Ubuntu and Windows 7.
Comment 3•8 years ago
|
||
(In reply to B.J. Herbison from comment #2)
> The test case behaves as expected for me, Enter activates the link.
>
> I tested on both Ubuntu and Windows 7.
You should enable e10s
Comment 4•8 years ago
|
||
(In reply to Alice0775 White from comment #3)
> You should enable e10s
Correctly identified, enabling e10s and the bug appears.
I also noted that in the test case pressing enter not only opens the Find Toolbar but also "erases" the previously found text. See the attached screen shot. (Windows 7. Not tested on Linux.) (I'm mentioning this here, but it might possibly be an effect which occurs in other circumstances.)
Comment 5•8 years ago
|
||
Comment 6•8 years ago
|
||
[Tracking Requested - why for this release]: Regression
Updated•8 years ago
|
Keywords: nightly-community
Updated•8 years ago
|
tracking-e10s:
--- → ?
Updated•8 years ago
|
tracking-e10s:
? → ---
Comment 7•8 years ago
|
||
Feature has been backed out so not tracking these bugs for 50.
tracking-firefox50:
? → ---
Comment 8•8 years ago
|
||
Bulk update to find bar bugs that won't be in 50 (according to https://bugzilla.mozilla.org/show_bug.cgi?id=1279695#c4 and local testing).
Comment 9•8 years ago
|
||
This was fixed in another bug.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 10•8 years ago
|
||
How can I test? last time I checked the new find in page was disabled in Nightly and the old wan was used.
Reporter | ||
Comment 11•8 years ago
|
||
I see the new search was reenabled in Nightly and now the issue is fixed :)
Thank you!
Comment 12•8 years ago
|
||
Verified as fixed on Nightly 51.0a1, build ID:20160914030200 on Windows 10 X64, Ubuntu 16.04 X64 and Mac OS X 10.11, using https://developer.mozilla.org/en-US/ page and the steps to reproduce from the Description and with testcase from comment 1.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•