Closed
Bug 587646
Opened 15 years ago
Closed 7 years ago
layout/generic/test/test_movement_by_words.html appears to be broken with 127 failures on Fennec
Categories
(Firefox for Android Graveyard :: General, defect, P1)
Tracking
(fennec-)
RESOLVED
WONTFIX
| Tracking | Status | |
|---|---|---|
| fennec | - | --- |
People
(Reporter: jmaher, Assigned: sayrer)
Details
(Whiteboard: [mobile_unittests] [mobile_dev_needed], fennec-testing,)
In testing fennec, I found that we have 127 failures on test_movement_by_words.html. In looking at this, we utilize the VK_LEFT and VK_RIGHT keys to iterate through various types of text. I believe that Fennec overloads these keys:
http://mxr.mozilla.org/mobile-browser/source/chrome/content/browser.xul#164
http://mxr.mozilla.org/mobile-browser/source/chrome/content/browser-ui.js#849
Can somebody confirm that these keys are directing the browser forward and backwards for Fennec instead of moving the cursor. If this is the case, we can disable this test for mobile platforms.
| Reporter | ||
Comment 1•15 years ago
|
||
hmm, test_backspace_delete.xul has 48 failures and relies on cmd_* move commands:
http://mxr.mozilla.org/mozilla-central/source/widget/src/gtk2/nsNativeKeyBindings.cpp#150
These commands seem to be the failing culprits:
Right (cmd_charNext)
Delete (cmd_deleteCharForward)
Backspace (cmd_deleteCharBackward)
| Reporter | ||
Updated•15 years ago
|
tracking-fennec: --- → ?
Updated•15 years ago
|
tracking-fennec: ? → 2.0-
Priority: -- → P1
| Reporter | ||
Updated•15 years ago
|
Whiteboard: mobile_unittests
| Assignee | ||
Updated•15 years ago
|
Assignee: nobody → sayrer
Whiteboard: mobile_unittests → mobile_unittests, fennec-testing
| Reporter | ||
Comment 2•15 years ago
|
||
can we get to the next steps on this bug?
Whiteboard: mobile_unittests, fennec-testing → [mobile_unittests] [mobile_dev_needed], fennec-testing,
Comment 3•7 years ago
|
||
Closing all opened bug in a graveyard component
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•