Stephany Wilkes Reporter
	Description • 10 years ago

This was observed in January and March user testing sessions. System wide, when typing is the only available action on the screen, we should bring up the keyboard. Doing so would help alleviate observed user confusion about what to do when faced with such screens, and would remove the extra tap for the user. 

Flagging Omega and Bruce to see if this might fit with existing Keyboard refresh work, but also flagging Harly since this may verge on Building Blocks territory.

	Omega Feng [:Omega] [:馮於懋]
	Comment 1 • 10 years ago

See bug 983043 for the UX spec update.

	Rudy Lu [:rudyl] (inactive after 2015/7/3)
	Comment 2 • 10 years ago

If this bug is about the general case intead of a specific scenario, like simpin dialog, as far as I know,
this should be controlled by each app.
An app could trigger the keyboard by focusing its focus at the right timing.

Stephany, could you confirm my understanding is correct?
If that is the case, we should change the component to Gaia and file separate issues on each app.

Thanks.

	Stephany Wilkes Reporter
	Comment 3 • 10 years ago

This is about the general case. I'll change the component and proceed as you suggest for 2.0 or 2.1 Rudy - thanks.

	Rudy Lu [:rudyl] (inactive after 2015/7/3)
	Comment 4 • 10 years ago

Then, I think this should be block bug 983043 (keyboard 2.0 update) if this in the general Gaia bucket.

	Rudy Lu [:rudyl] (inactive after 2015/7/3)
	Comment 5 • 10 years ago

(In reply to Rudy Lu [:rudyl] from comment #4)
> Then, I think this should be block bug 983043 (keyboard 2.0 update) if this
                          s/be/not/
> in the general Gaia bucket.

	BMO Automation
	Comment 6 • 6 years ago

Firefox OS is not being worked on