Closed Bug 956170 Opened 10 years ago Closed 10 years ago

[keyboard refactor] backport new keyboard visuals

Categories

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

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: djf, Assigned: djf)

References

Details

Attachments

(2 files, 2 obsolete files)

The new keyboard CSS that landed in 1.3 needs to be copied to the refactored keyboard in progress in test_apps/demo-keyboard.
Summary: port new keyboard visuals to refactored keyboard app → [keyboard refactor] backport new keyboard visuals
Assignee: nobody → dflanagan
I finally had time to finish a patch! Would you review, please, Jan?
Attachment #8359077 - Flags: review?(janjongboom)
Hi David, the demo keyboard has some visual differences compared to master keyboard (not taking the suggestion bar into account):

* All chars seem to be bold
* Bottom row seems to be higher
* Text color of special keys (SHIFT, SPACE, etc.) does not match

See screenshots (taken from Keon device).
Flags: needinfo?(dflanagan)
Thanks, Jan.  I was going to leave that fine level of detail to a UX review later, but I'll address the issues you've identified and try to get the screens matching more exactly.
Flags: needinfo?(dflanagan)
Do you want me to run the UI tests against the new keyboard as well, or is that too early? Will require some changes in HTML attributes.
Attachment #8359077 - Flags: review?(janjongboom)
Comment on attachment 8359077 [details] [review]
link to patch on github

I've updated the pull request to fix the visual nits you identified, and a couple of others as well.  Please review again.
Attachment #8359077 - Flags: review?(janjongboom)
(In reply to Jan Jongboom [:janjongboom] from comment #6)
> Do you want me to run the UI tests against the new keyboard as well, or is
> that too early? Will require some changes in HTML attributes.

I don't even know what the UI tests do... What changes will be needed?
The UI tests test the actual behavior of the keyboard. But it identifies the keys by CSS selectors. So we would make sure that those keys can still be found.
I've been trying out, and you can see a weird bug (the background flashing is not specific to this keyboard). It happens in the last switch of this video. You see that the keys are not laid out properly. Any clue?
Attachment #8359785 - Attachment is obsolete: true
Attachment #8359786 - Attachment is obsolete: true
Flags: needinfo?(dflanagan)
I can see something different flashes on the last transition in the video, but then once you move your hand away I can't tell what is wrong about the layout...

Can you reproduce it again and attach a screenshot? 

Also, are you sure that it is the new keyboard with the bad layout and not the old one? If you typed a character so you weren't at the start of a sentence, the new keyboard would display lowercase and the old one would display upper so we could tell them apart more easily.

Could this be related to bug 959200?
Flags: needinfo?(dflanagan)
Flags: needinfo?(janjongboom)
Hmm, I don't know, it's like the keys are positioned wrongly and then a reflow happens and it's OK. I think we should just land this patch and see if we can find out what causes it in follow up.
Flags: needinfo?(janjongboom)
Okay.  I'll take that as an implict r+, and will set the flag.
Comment on attachment 8359077 [details] [review]
link to patch on github

review was by Jan; I'm just setting the r+ flag for him
Attachment #8359077 - Flags: review?(janjongboom) → review+
Landed to master: https://github.com/mozilla-b2g/gaia/commit/8e09479b0d2b4865917113eeef7b5e45aa8161fa
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: