Ticket #1693 (closed defect: fixed)

Opened 3 months ago

Last modified 3 months ago

In Safari Keyboard-shortcuts not active if no component is explicitly focused

Reported by: Joonas Lehtinen Owned by: Marc Englund
Priority: trivial Milestone: User Interface Library 5.2.3
Component: gwt-adapter-client Version: 5.2.0-rc
Keywords: Cc:
Known Issue description:
Hours estimate: Deadline (dd.mm.yyyy):
Known Issue version (since): Known Issue title:
Hours done: Depends to:
Affects documentation: no
Known Issue workaround:
Affects release notes: yes Contract:

Description (last modified by Matti Tahvonen) (diff)

Note, this is issue only for Safari. With Webkit this works like with other browsers.

In keyboard shortcut-demo no shortcuts are passed to application when one clicks inside the window, but does not focus one of the components. Should we have somekind of "hidden" component that could be focused by default when clicking window-area or loading the page in order to make shortcuts seem more intuitive?

Change History

Changed 3 months ago by Matti Tahvonen

  • priority changed from minor to trivial
  • description modified (diff)
  • summary changed from Keyboard-shortcuts not active if no component is explicitly focused to In Safari Keyboard-shortcuts not active if no component is explicitly focused

Changed 3 months ago by Joonas Lehtinen

  • milestone set to User Interface Library 5.2.1

Changed 3 months ago by Joonas Lehtinen

  • milestone changed from User Interface Library 5.2 backlog to User Interface Library 5.2.2

Milestone User Interface Library 5.2 backlog deleted

Changed 3 months ago by Matti Tahvonen

  • status changed from new to closed
  • resolution set to fixed

in [4826]

Changed 3 months ago by Matti Tahvonen

  • status changed from closed to reopened
  • resolution deleted

my bad still an issue in Safari, Nightly webkit ok.

Changed 3 months ago by Joonas Lehtinen

Would it be possible to make a workaround for the current safari or is the only alternative just declare this as a known safari limitation that will be fixed in Safari 4?

Changed 3 months ago by Matti Tahvonen

  • status changed from reopened to closed
  • resolution set to fixed

in [4854].

Note, this needs [4853] (in case change is merged to 5.2.x)

Note: See TracTickets for help on using tickets.