Bug 83027

Summary: Input element in a fullscreened iframe accepts some typed characters when it should not
Product: WebKit Reporter: Vladislav Kaznacheev <kaznacheev>
Component: FramesAssignee: Nobody <webkit-unassigned>
Status: RESOLVED WONTFIX    
Severity: Normal CC: fred.wang, jeremya, jer.noble
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 276855    
Attachments:
Description Flags
Archive containing two files that need to be unpacked next to each other (one is the main html file, the other is an iframe content)
none
updated testcase with modern APIs none

Vladislav Kaznacheev
Reported 2012-04-03 06:37:48 PDT
1. Download and unpack the attach archive. 2. Open fullscreen_main.html 3. Click on "Click here to toggle fullscreen" button. The browser would go fullscreen. 4. Click on an input field with the text "Type here...". 5. Try typing there. Expected result: no character should appear since Element.ALLOW_KEYBOARD_INPUT is not passed to the fullscreen request call Actual result: Chromium ToT: 0-9 and a-h do not appear when typed, j-z do appear. Safary 5.1.2: ":'\/." do appear
Attachments
Archive containing two files that need to be unpacked next to each other (one is the main html file, the other is an iframe content) (1.35 KB, application/zip)
2012-04-03 06:48 PDT, Vladislav Kaznacheev 		no flags
Details
updated testcase with modern APIs (2.67 KB, text/html)
2026-10-12 08:37 PDT, Frédéric Wang Nélar 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Vladislav Kaznacheev
Comment 1 2012-04-03 06:48:51 PDT
Created attachment 135321 [details] Archive containing two files that need to be unpacked next to each other (one is the main html file, the other is an iframe content)
Frédéric Wang Nélar
Comment 2 2026-10-12 08:37:43 PDT
Created attachment 481768 [details] updated testcase with modern APIs
Frédéric Wang Nélar
Comment 3 2026-10-12 08:41:55 PDT
For me Chrome and Safari allows content to be type. I think this is obsolete API though so I would close this as WONTFIX. I uploaded a testcase with modern API and keyboardLock but I think this serves different purpose.
Note You need to log in before you can comment on or make changes to this bug.