Closed Bug 870648 Opened 12 years ago Closed 7 years ago

[Buri][IOT][MMI] Activation / deactivation of predictive text by pressing a simple key or softkey is not possible

Categories

(Firefox OS Graveyard :: Gaia::Keyboard, defect, P1)

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-b2g:-)

RESOLVED WONTFIX
blocking-b2g -

People

(Reporter: sync-1, Unassigned)

References

Details

(Whiteboard: Chile, IOT, buri)

SW129,SW1U6 AU_LINUX_GECKO_ICS_STRAWBERRY_V1.01.00.01.019.094 Firefox os v1.0.1 Mozilla build ID:20130502070201 +++ This bug was initially created as a clone of Bug #451160 +++ DEFECT DESCRIPTION: Please confirm if it is possible (or platform limitation) to add some option in keyboard to do activation and deactivation of predictive test in the same interface of SMS writing. EXPECTED BEHAVIOUR: The process of activating/de-activating the predictive text imput must be as simple and intuitive as possible. The selected mode has to be kept as default mode and user must be able to change it from keyboard SMS interface. REPRODUCING PROCEDURES: step instructions to reproduce): 1. Go into DuT messaging menu and edit a message. 2. Check that the activation and deactivation of predictive mode is as simple as possible either by pressing a key or a soft key on DuT. 3. Check that by default the predictive text is deactivated. 4. Check that once the user selects the predictive text, this mode is set as the new default mode (even after power cycling the DuT). Could you include any option to do activation and deactivation in the same keyboard, for example by doing a long press in the "tab" key. ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT: Improve MMI REPRODUCING RATE: 100% For FT PR, Please list reference mobile's behavior: ++++++++++ end of initial bug #451160 description ++++++++++ CONTACT INFO (Name,Phone number): DEFECT DESCRIPTION: REPRODUCING PROCEDURES: EXPECTED BEHAVIOUR: ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT: REPRODUCING RATE: For FT PR, Please list reference mobile's behavior:
blocking-b2g: --- → tef?
Whiteboard: Chile, IOT, buri
this seem like a feature request. is this a blocker from OBs? David? Thanks
Flags: needinfo?(dpv)
Not a blocker in OBs
Flags: needinfo?(dpv)
per comment 2, tef-, koi? for future consideration
blocking-b2g: tef? → koi?
Component: Gaia::SMS → Gaia::Keyboard
This issue is not a blocker for the OBs. If we plan to include a new feature like this, IMHO we should consider to access the whole keyboard settings instead of only predective text setting. BTW,the availabe space in current keyboard design is not enough to include a new key and make a user friendly setting access, Why dont we use the typing bar(by long press for example) to access the keyboard settings?
I agree a quick access to keyboard settings would be interesting. However, the current layout doesn't offer too much space for an additional key once several languages are available. That said, I think we could come up with other solutions involving gestures and/or long-press actions on easy targets like the space bar or the whole keyboard.
Not taking feature request for v1.2 at this moment.
blocking-b2g: koi? → 1.3?
Not blocking on this for 1.3. Carrie, are there any plans to include access to keyboard settings directly from keyboard?
blocking-b2g: 1.3? → -
Flags: needinfo?(cawang)
I haven't seen any plans in the mockups.
Hi everyone, We've included this quick access in 1.3 KB spec and will release it after internal review. Thanks!
Flags: needinfo?(cawang)
Do we really have this feature planned?
feature-b2g: --- → 2.2?
Flags: needinfo?(ofeng)
No we don't have this feature planned, but still ni? Bruce to confirm it.
Flags: needinfo?(ofeng) → needinfo?(bhuang)
I'm leaning towards having the spec in bug 985851 cover this.
Flags: needinfo?(bhuang)
feature-b2g: 2.2? → ---
Firefox OS is not being worked on
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.