Closed
Bug 759437
Opened 13 years ago
Closed 4 years ago
Consider inserting spaces in AwesomeBar between words in committed by Swype after the user manually enters a space
Categories
(Firefox for Android Graveyard :: Keyboards and IME, enhancement, P4)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: cpeterson, Unassigned)
References
Details
(Whiteboard: VKB)
STR:
1. Open AwesomeScreen
2. Using Swype VKB, enter a search phrase with multiple words like "download firefox mobile android"
AR:
Unlike Swype text entry in other forms, the AwesomeScreen requires you to manually insert a space between each word.
ER:
It would be convenient if the first manually-entered space shifts AwesomeScreen text entry into an "auto-insert subsequent spaces between whole words committed from Swype" mode.
| Reporter | ||
Updated•13 years ago
|
Priority: -- → P4
| Reporter | ||
Comment 1•13 years ago
|
||
bnicholson and I have sketched out a new (but untested) heuristic for Swype behavior in the AwesomeBar:
1. Initial AwesomeBar mode = SEARCH.
2. If IME == Swype, then tell Swype to auto-insert spaces between words.
3. If mode == SEARCH and Swype user enters '.' or ':' (or '/'?), then mode = URL (so Swype will stop inserting spaces).
4. If Swype user enters ' ', then revert to mode = PERMA_SEARCH (so step #3 does not re-enter URL mode).
Brian suggested a simpler algorithm that may have slightly more overhead:
1. Look at the whole string every time the text changes.
2. If there's a '.' and no ' ', then URL mode is on; otherwise it's off
Summary: Consider inserting spaces in AwesomeScreen between words in committed by Swype after the user manually enters a space → Consider inserting spaces in AwesomeBar between words in committed by Swype after the user manually enters a space
| Reporter | ||
Comment 2•13 years ago
|
||
WONTFIX because bug 767597 was a better (and less complicated) solution.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
| Reporter | ||
Comment 3•13 years ago
|
||
Reopening because bnicholson pointed out that this bug is a complement to bug 767597, not an alternative.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
| Reporter | ||
Updated•13 years ago
|
Assignee: nobody → cpeterson
| Reporter | ||
Updated•12 years ago
|
Assignee: cpeterson → nobody
Status: REOPENED → NEW
Comment 4•4 years ago
|
||
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 13 years ago → 4 years ago
Resolution: --- → INCOMPLETE
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•