Note: There are a few cases of duplicates in user autocompletion which are being worked on.

Status

()

Core
DOM: Events
--
enhancement
UNCONFIRMED
6 years ago
6 years ago

People

(Reporter: Boaz Sender, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_0) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.106 Safari/535.2




Expected results:


* Use case
  * When I crouch and walk forward in a game, the window should not close
* Request description
  * allow developer to lock keyboard. Similar to emerging mouselock spec.
* Target W3C group
  * Web events group
* Traction
  * chrome issue: http://code.google.com/p/chromium/issues/detail?id=84332
  * chrome design doc draft: https://sites.google.com/a/chromium.org/dev/developers/design-documents/reserved-keys-api
(Reporter)

Updated

6 years ago
OS: Mac OS X → All
Hardware: x86 → All

Comment 1

6 years ago
Why would the window close when you are crouching and walking? If you have focus on a canvas object or something and press say ctrl+w it doesn't close the window in any browser.
Severity: normal → enhancement
Component: General → DOM: Events
QA Contact: general → events

Comment 2

6 years ago
(In reply to warcraftthreeft from comment #1)
> If you have
> focus on a canvas object or something and press say ctrl+w it doesn't close
> the window in any browser.

That should not be true in Chrome, where we prevent some keystrokes (e.g. ctrl-w) from being sent to webpages by default so badly-behaving pages don't result in the user being unable to close/change tabs, etc.

Comment 3

6 years ago
Woah, you're right. I just tested it with one of my canvas projects. Backspace goes back a page in Chrome (along with the ctrl+w close). I guess this is needed. Didn't realize user agents could take precedent over a web page with focus and key events.
You need to log in before you can comment on or make changes to this bug.