ubuntu-sdk-bugs team mailing list archive

[Matthew Paul Thomas <mpt@xxxxxxxxxxxxx>]

Specification updated. <https://goo.gl/CJ1YLB> However, that is
unfortunately a Canonical-only link, toolkit spec changes in general
require approval from someone who is not available today, and they
aren't visible to others until they are approved.

So for convenience, here's what I wrote:
------------
The on-screen keyboard should appear if:
* no external keyboard is connected, and a text field becomes focused; or
* an external keyboard is connected, but the most recent text typed anywhere was with the OSK, and a text field becomes focused; or
* an external keyboard is connected, and the most recent text typed was with an external keyboard, but you tap in the already-focused text field. (App developers are responsible for emulating this behavior in typable areas that are not text fields.)
------------

This avoids having to design a visual element for, valuable screen space
being taken up by, and users having to learn, a separate control for
revealing the OSK. If it doesn't appear when they want it to, they can
just do what they'd probably try doing anyway, which is tapping again
where they want to type.

Meanwhile, this bug report seems to have morphed from the original
problem of Ubuntu believing a mouse when it claims to be a keyboard. Is
there a separate bug report for that now?

** Changed in: ubuntu-ux
       Status: In Progress => Fix Committed

** Package changed: unity8 (Ubuntu) => ubuntu-ui-toolkit (Ubuntu)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
       Status: Incomplete => Triaged

** Description changed:

  There are mice on the market that claim to be keyboards as well. This
  inhibits OSK. We can try and find out how many keys they have and be
  smart about it.
  
  Regardless, we should have a way of forcing the OSK, especially on
  touch-enabled devices. Whether it's triggered by a touch (as opposed to
  mouse click) on the text area, or with a button in the text field
  (replaced with the clear icon when you start typing). Another option is
  the copy/paste dropdown.
  
- We should also define what happens when focusing a text field after the
- user forced the OSK to show up. Does it come up every time until the
- user dismisses it? Or only when they force it?
+ <https://goo.gl/CJ1YLB>:
+ ------------
+ The on-screen keyboard should appear if:
+ * no external keyboard is connected, and a text field becomes focused; or
+ * an external keyboard is connected, but the most recent text typed anywhere was with the OSK, and a text field becomes focused; or
+ * an external keyboard is connected, and the most recent text typed was with an external keyboard, but you tap in the already-focused text field. (App developers are responsible for emulating this behavior in typable areas that are not text fields.)
+ ------------
  
  == original description ==
  
  1. Boot nexus 7
  2. In the login screen, test that OSK works by tapping the password textfield
  3. swipe keyboard back down after testing it works
  4. Turn on Bluetooth mouse to get a mouse cursor
  5. Click on password textfield
  
  OSK doesn't pop up, touch tapping on the field doesn't bring up the OSK
  anymore either.
  
  ie. The login screen is not usable with mouse connected - cannot type in
  password via OSK since it doesn't come up when clicking the password
  textfield with mouse.
  
  See attached screenshot. Focus on textfield. Would expect OSK to show
  up.

-- 
You received this bug notification because you are a member of Ubuntu
SDK bug tracking, which is subscribed to ubuntu-ui-toolkit in Ubuntu.
https://bugs.launchpad.net/bugs/1521518

Title:
  No way to invoke OSK when a hardware keyboard is connected

Status in canonical-pocket-desktop:
  Incomplete
Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  There are mice on the market that claim to be keyboards as well. This
  inhibits OSK. We can try and find out how many keys they have and be
  smart about it.

  Regardless, we should have a way of forcing the OSK, especially on
  touch-enabled devices. Whether it's triggered by a touch (as opposed
  to mouse click) on the text area, or with a button in the text field
  (replaced with the clear icon when you start typing). Another option
  is the copy/paste dropdown.

  <https://goo.gl/CJ1YLB>:
  ------------
  The on-screen keyboard should appear if:
  * no external keyboard is connected, and a text field becomes focused; or
  * an external keyboard is connected, but the most recent text typed anywhere was with the OSK, and a text field becomes focused; or
  * an external keyboard is connected, and the most recent text typed was with an external keyboard, but you tap in the already-focused text field. (App developers are responsible for emulating this behavior in typable areas that are not text fields.)
  ------------

  == original description ==

  1. Boot nexus 7
  2. In the login screen, test that OSK works by tapping the password textfield
  3. swipe keyboard back down after testing it works
  4. Turn on Bluetooth mouse to get a mouse cursor
  5. Click on password textfield

  OSK doesn't pop up, touch tapping on the field doesn't bring up the
  OSK anymore either.

  ie. The login screen is not usable with mouse connected - cannot type
  in password via OSK since it doesn't come up when clicking the
  password textfield with mouse.

  See attached screenshot. Focus on textfield. Would expect OSK to show
  up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1521518/+subscriptions