Closed
Bug 1156695
Opened 9 years ago
Closed 8 years ago
Keypresses are lost on Ctrl+F before toolbar is ready
Categories
(Toolkit :: Find Toolbar, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1218351
People
(Reporter: from_bugzilla3, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:39.0) Gecko/20100101 Firefox/39.0 Build ID: 20150413140831 Steps to reproduce: 1. To ensure the best chance of reproducing, launch a sluggish Firefox profile. (eg. extensions, far too many open tabs, etc.) 2. Hit Ctrl+F and start typing in rapid succession Actual results: The first few characters of what I typed were missing (eg. I typed "<Ctrl+F>iso" and the search bar wound up looking for "o") Expected results: Every character typed after Ctrl+F should have ended up in the search field.
Comment 1•8 years ago
|
||
User Agent Mozilla/5.0 (X11; Linux x86_64; rv:46.0) Gecko/20100101 Firefox/46.0 Build ID 2015121603022 I tried to reproduce on Nightly 46 and it works fine for me, with many open tabs and extensions installed. Is this issue still reproducing for you when using newly Firefox versions (Firefox 43 https://www.mozilla.org/en-US/firefox/new/ or Firefox 46 https://nightly.mozilla.org/)?
Flags: needinfo?(from_bugzilla2)
Reporter | ||
Comment 2•8 years ago
|
||
I'm still getting it on Aurora 45 with my usual profile but, since my browser isn't bogged down at the moment, I wasn't able to trigger it until I remembered how horrendously slowly Amazon.ca page loads go when the browser is already bogged down. I'm a bit behind on various obligations at the moment, but I'll try to fit in a re-test under a clean 43 or 46 profile as soon as possible.
Component: Untriaged → Find Toolbar
Product: Firefox → Toolkit
Summary: Keypresses after Ctrl+F but before toolbar is ready are lost → Keypresses are lost on Ctrl+F before toolbar is ready
Updated•8 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Flags: needinfo?(from_bugzilla2)
Resolution: --- → DUPLICATE
Reporter | ||
Comment 4•8 years ago
|
||
For the record, I've been experiencing this since before e10s was an option in Aurora and I keep e10s turned off because I'm still waiting for all of my extensions to become fully compatible. (Most irreplaceably, NoScript)
Comment 5•8 years ago
|
||
Then it would be bug 1198465 which has been fixed already. Please do let us know if you still experience this in either case.
Reporter | ||
Comment 6•8 years ago
|
||
When did that fix move from Nightly to Aurora? Because it says it was fixed in November and targeted at 45 but I mentioned that I replicated it in Aurora 45 as provided by the Ubuntu PPA on 2015-12-17.
Comment 7•8 years ago
|
||
That hit Nightly in 45.
Reporter | ||
Comment 8•8 years ago
|
||
(In reply to Luís Miguel [:quicksaver] from comment #7) > That hit Nightly in 45. What I mean is that I'm not very clear on the criteria for things moving from Nightly to Aurora outside of the normal "ride the trains" flow. As such, I don't know at what point the fix would have landed (or will land) in my browser.
Comment 9•8 years ago
|
||
Bug 1198465 landed in Nightly in 45, which means it has been in Aurora 45 since its first build. If you still experience the issue, then it's still likely bug 1218351 which, despite the name, can in theory still affect non-e10s environments on very extreme circumstances. If after bug 1218351 is fixed you still experience the issue just let me know and I'll be sure to reopen the bug if necessary. ;)
You need to log in
before you can comment on or make changes to this bug.
Description
•