Closed
Bug 682017
Opened 14 years ago
Closed 14 years ago
Remove CustomKeySender and use content KeyEvents forwarding
Categories
(Firefox for Android Graveyard :: General, defect)
Firefox for Android Graveyard
General
Tracking
(Not tracked)
RESOLVED
FIXED
Firefox 10
People
(Reporter: romaxa, Assigned: romaxa)
References
Details
Attachments
(1 file)
3.40 KB,
patch
|
mfinkle
:
review+
mfinkle
:
feedback+
|
Details | Diff | Splinter Review |
I think it is time to remove CustomKeySender from fennec and switch to dom/IPC content key events forwarding
Assignee | ||
Comment 1•14 years ago
|
||
Assignee | ||
Comment 2•14 years ago
|
||
Comment on attachment 555777 [details] [diff] [review]
Kill CustomKeySender
Don't have android with keyboard, can someone try this:
http://tbpl.allizom.org/?tree=Try&usebuildbot=1&rev=c08f956fcab1
http://stage.mozilla.org/pub/mozilla.org/firefox/try-builds/romaxa@gmail.com-c08f956fcab1/try-android/
?
Attachment #555777 -
Flags: feedback?(mark.finkle)
Comment 3•14 years ago
|
||
Comment on attachment 555777 [details] [diff] [review]
Kill CustomKeySender
Looks ok. Oleg, can you briefly talk about why this is not needed anymore? Where is the magic happening now? Can we cleanup any code in the content.js file too?
Attachment #555777 -
Flags: feedback?(mark.finkle) → feedback+
Assignee | ||
Comment 4•14 years ago
|
||
Magic happening here:
https://bugzilla.mozilla.org/show_bug.cgi?id=583976
Not sure about content part, probably I need to take my N950 with HW keyboard and check it .
Assignee | ||
Comment 5•14 years ago
|
||
Comment on attachment 555777 [details] [diff] [review]
Kill CustomKeySender
No we should not remove content keys stuff... otherwise key events short cuts will not work.
With attached patch it works fine, shortcuts and general text input.
Tested on N900 (don't have android with keyboard)
Attachment #555777 -
Flags: review?(mark.finkle)
Comment 6•14 years ago
|
||
Comment on attachment 555777 [details] [diff] [review]
Kill CustomKeySender
OK, let's give this a try
Attachment #555777 -
Flags: review?(mark.finkle) → review+
Assignee | ||
Updated•14 years ago
|
Keywords: checkin-needed
Comment 7•14 years ago
|
||
In my queue with a few other bits that are being sent to try first and then onto inbound.
Assignee | ||
Comment 8•14 years ago
|
||
It actually has been on try already: see 682017#c2
Comment 9•14 years ago
|
||
Sorry missed that, however the other items needed to go through try anyway and batching a few checkin-neededs at once when pushing to inbound saves a bunch of build pool time.
Comment 10•14 years ago
|
||
Target Milestone: --- → Firefox 9
Comment 11•14 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 12•14 years ago
|
||
backed out. caused 684558.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 13•14 years ago
|
||
Try run is green: https://tbpl.mozilla.org/?tree=Try&usebuildbot=1&rev=cdb8f52e8801
Pushed to inbound along with regression fixes (bug 683736 and bug 684558):
https://hg.mozilla.org/integration/mozilla-inbound/rev/f0991759b732
Status: REOPENED → ASSIGNED
OS: Linux → All
Hardware: x86 → All
Target Milestone: Firefox 9 → Firefox 10
Comment 14•14 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•