Closed Bug 905482 Opened 11 years ago Closed 10 years ago

[Flatfish][Keyboard] add support for large device

Categories

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

Other
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1065893

People

(Reporter: gasolin, Unassigned)

References

Details

(Whiteboard: [flatfish][TCP=feature-p1])

Attachments

(2 files)

Expect: Modify and Merge experiment tablet work from https://github.com/gaia-local/gaia to master
Blocks: flatfish
OS: Mac OS X → Gonk (Firefox OS)
Hardware: x86 → Other
Attached image Keyboard_in_mail
Use mail's Compose page as keyboard's example.
It's a must for flatfish. Marked as koi+ according to triage result.
blocking-b2g: --- → koi+
Whiteboard: [Flatfish only]
Mike, is there any keyboard UX spec that we should follow?
Flags: needinfo?(mtsai)
Yes, first Spec is coming out on 10/15~10/17.
Flags: needinfo?(mtsai)
Depends on: 923866
Minus it because functionally work in koi already. This is bug for tablet feature work.
blocking-b2g: koi+ → -
Nominate for v1.3. We have a spec update here, and according to UX suggestion, we can focus on layout update first and keep the visual style as is.
blocking-b2g: - → 1.3?
De-nominate this as we're waiting for the confirmation of layout change for tablet.
blocking-b2g: 1.3? → ---
Have you received now confirmation of layout change for tablet ? I'm contributor to the Tablet Contribution Program and it will be now very interesting to get a better keyboard for my Flashfish device.
Not wanting to add noise, but will this cover contextual inputs? Currently when typing in the URL bar on Flatfish there is now forward slash present.
Not sure if the spec is the final version. So ni our UX with bug 906552 comment 7. (In reply to Caspy7 from comment #10) > Not wanting to add noise, but will this cover contextual inputs? > Currently when typing in the URL bar on Flatfish there is now forward slash > present. If this is about the URL bar in the browser app, that should be a separate issue, and we had an old debate about it. This is as is because that is not just a URL bar but also a search bar, so we have to use type="text" for that input field, and keyboard won't show "/" for type="text".
Bug 906552 comment 8 has the answer to this. "Not yet. For tablet Keyboard, as I know, the UX spec would be done at the end of July, and visual spec at the end of August. The schedule may still change."
Blocks: flatfish-ux
No longer blocks: flatfish
Whiteboard: [Flatfish only] → [flatfish]
Whiteboard: [flatfish] → [flatfish][TCP=feature-p1]
It would be a nice feature if the keyboard had the arrow keys like a physical one. Very often I find it difficult to move among the single letters of a small text field, I have to tap so many times till I succeed selecting the wanted position. On the first use, I had problem understanding how to type some characters like square brackets []. I am new to touch devices so it could be a common problem to users in my own condition (no, I wasn't drunk). I have seen that the layout has been slightly changed in the latest build (I refer to today's one, Build identifier: 20140814012429, Git commit info: a2219a55) and that "ALT" is now "Alt". Maybe a different background colour just for that specific button could improve usability.
Current keyboard is extremely uncomfortable - it is too large, keys are too far from each other. On tablet there is so much space that many additional keys can be put in default view of keyboard (i.e. comma, colon, at ('@') and etc. It would be a good idea to allow users to set size of keyboard as well - in such situation those who want have it smaller to write faster could do that and those who really need huge keys also have chance to get it. Tested on: Foxconn InFcocus F1 tablet (TCP) B2G version: 2.1.0.0-prerelease master Platform version: 34.0a1 Build Identifier: 20140815012352 Git commit info: 2014-08-14 16:21:42 e57ea931
Flags: needinfo?(ffos-product)
Moving needinfo to Bruce.
Flags: needinfo?(bhuang)
Flags: needinfo?(ffos-product)
Adding Omega on UX
Flags: needinfo?(bhuang) → needinfo?(ofeng)
We'll have new UX design for tablet keyboard in early Sep.
See bug 1065893 for the latest UX spec for tablet.
Flags: needinfo?(ofeng)
Should we close this bug and move work to bug 1065893?
(In reply to Joshua Smith [:joshua-s] from comment #21) > Should we close this bug and move work to bug 1065893? +1
Closed! This issue is being addressed by bug 1065893.
No longer blocks: flatfish-ux, 1065893
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: