Closed
Bug 1411604
Opened 8 years ago
Closed 8 years ago
On Facebook, the search results are not updated when adding new characters to the initial searched term
Categories
(Core :: DOM: Events, defect, P2)
Core
DOM: Events
Tracking
()
RESOLVED
WORKSFORME
| Tracking | Status | |
|---|---|---|
| firefox56 | --- | unaffected |
| firefox57 | --- | fix-optional |
| firefox58 | --- | unaffected |
| firefox59 | --- | unaffected |
People
(Reporter: roxana.leitan, Unassigned)
References
Details
(Keywords: regression)
Attachments
(1 file)
|
360.73 KB,
video/mp4
|
Details |
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0
Build ID: 20171024220325
[Affected versions]:
Nightly 58.0a1
[Affected platforms]:
Windows 10 x 64, Mac OS X 10.12
[Steps to reproduce]:
1.Launch Firefox with a new profile
2.Login to Facebook.com
3.Type something in the search bar ( e.g. "tes")
4.Add characters to the term searched in step 3 (e.g."t")
[Expected result]:
The search results and "Find more results for.." section should be updated
[Actual result]:
The search results and the "Find more results for.." section are not updated with the latest searched term
Comment 1•8 years ago
|
||
Not completely sure where this bug belongs, but Firefox::Search is for the internal search, not any website ("Search Web search UI, default search engines and Toolkit's search service").
Component: Search → Untriaged
Roxana, can you get a regression range for Firefox, or is this a change on the facebook.com? If a change to facebook, then we can get this to webcompat
Flags: needinfo?(roxana.leitan)
Tested with 3 Facebook accounts and I can reproduce the issue only in my account.
Last good revision: d6e1c5f5a5c3548e06135b851c7e39af080b492e
First bad revision: 665ea291fce432c014fa48dedc94f204f3dd1fb4
Pushlog:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=d6e1c5f5a5c3548e06135b851c7e39af080b492e&tochange=665ea291fce432c014fa48dedc94f204f3dd1fb4
Flags: needinfo?(roxana.leitan)
Comment 4•8 years ago
|
||
(In reply to roxana.leitan@softvision.ro from comment #3)
> Tested with 3 Facebook accounts and I can reproduce the issue only in my
> account.
Wondering is it intermittent or always reproducible with your account? Tested with my account but cannot reproduce it.
Updated•8 years ago
|
status-firefox56:
--- → unaffected
status-firefox57:
--- → affected
Comment 6•8 years ago
|
||
I saw the video and it's about the search in facebook. Wondering which Gecko components may be related to the search functionality?
Comment 7•8 years ago
|
||
The search functionality seems to be implemented by the content. Removing an 'input' event listener on the input element breaks it.
Updated•8 years ago
|
Flags: needinfo?(mitaylor)
Updated•8 years ago
|
Priority: -- → P2
Comment 9•8 years ago
|
||
Roxana, if you toggle input_event_queue.supported to false, does the bug still reproduce in your profile?
Flags: needinfo?(roxana.leitan)
Comment 10•8 years ago
|
||
Tom, could you please have a look? I'm on PTO!
Flags: needinfo?(dschubert) → needinfo?(twisniewski)
| Reporter | ||
Comment 11•8 years ago
|
||
Is not reproducible with "input_event_queue.supported" set to false.
Flags: needinfo?(roxana.leitan)
Comment 12•8 years ago
|
||
I can't reproduce precisely the same bug, but I *am* able to reproduce something similar on Linux, and on Windows 10 (the Quantum reference hardware).
1) Do a search for "testt": click the FB search bar, type "testt", seems to be working.
2) Leaving the focus on the search bar, hit ESC. The search is cleared as expected, with the focus remaining on the search bar.
3) Do another search for "testt": the first t is forgotten as the e is typed, and the search ends up being for "estt".
This bug does *not* go away when "input_event_queue.supported" is set to false, and it happens for me in Chrome as well. Nothing is logged in the web console.
Roxana, could you check if your bug happens for you in Chrome as well? They may be unrelated. If so, is anything interesting logged in the web console on your end?
Flags: needinfo?(twisniewski) → needinfo?(roxana.leitan)
| Reporter | ||
Comment 13•8 years ago
|
||
Hi Thomas,
The bug is not reproducible in Chrome.
Nothing logged in the web console or browser console.
Flags: needinfo?(roxana.leitan)
Updated•8 years ago
|
Flags: needinfo?(mitaylor)
| Reporter | ||
Comment 14•8 years ago
|
||
I cannot reproduce this issue using the latest Nightly 59.0a1 (2018-01-07), the latest Firefox Beta 58.0b14 and Firefox RC 57.0.4 on Windows 10 x64 and Mac OS X 10.12.
I will mark this bug Resolved-WFM.
Status: NEW → RESOLVED
Closed: 8 years ago
status-firefox59:
--- → unaffected
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•