touch-packages team mailing list archive

[Andrea Bernabei <andrea.bernabei@xxxxxxxxxxxxx>]

Public bug reported:

r1767

InputHandler handles Pg_UP and Pg_DOWN keys, but doesn't stop the key event from propagating.
That results in both the input handler and its parents getting and handling the key event.

Concrete example:
- Focus on TextArea, use Pg_UP to scroll up in the text field
- TextArea will scroll up
- If TextArea's ancestors includes ScrollView (not yet released) or any other component that handles the same keys, that component will receive the events as well, and both will act at the same time.

This is probably not what we want :)

Key events in QML are not consume by default, so we have to explicitly
set "event.accepted = true" to stop a key event from propagating up the
hierarchy.

** Affects: ubuntu-ui-toolkit (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

  r1767
  
  InputHandler handles Pg_UP and Pg_DOWN keys, but doesn't stop the key event from propagating.
  That results in both the input handler and its parents getting and handling the key event.
  
  Concrete example:
  - Focus on TextArea, use Pg_UP to scroll up in the text field
  - TextArea will scroll up
  - If TextArea's ancestors includes ScrollView (not yet released) or any other component that handles the same keys, that component will receive the events as well, and both will act at the same time.
  
  This is probably not what we want :)
+ 
+ Key events in QML are not consume by default, so we have to explicitly
+ set "event.accepted = true" to stop a key event from propagating up the
+ hierarchy.

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

Title:
  InputHandler doesn't consume the Key events it handles

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  r1767

  InputHandler handles Pg_UP and Pg_DOWN keys, but doesn't stop the key event from propagating.
  That results in both the input handler and its parents getting and handling the key event.

  Concrete example:
  - Focus on TextArea, use Pg_UP to scroll up in the text field
  - TextArea will scroll up
  - If TextArea's ancestors includes ScrollView (not yet released) or any other component that handles the same keys, that component will receive the events as well, and both will act at the same time.

  This is probably not what we want :)

  Key events in QML are not consume by default, so we have to explicitly
  set "event.accepted = true" to stop a key event from propagating up
  the hierarchy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1526384/+subscriptions