Bug 116925 - A focused element should lose focus when it becomes unfocusable
Summary: A focused element should lose focus when it becomes unfocusable
Status: RESOLVED DUPLICATE of bug 112992
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: BlinkMergeCandidate
Depends on:
Blocks:
 
Reported: 2013-05-29 00:34 PDT by Ryosuke Niwa
Modified: 2013-05-29 01:00 PDT (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ryosuke Niwa 2013-05-29 00:34:38 PDT 
Consider merging https://chromium.googlesource.com/chromium/blink/+/c58f636fd18fc27944c42e27d6a92a36867c57e1

According to the specification, we should remove focus when a focused element
becomes unforcusable, and Internet Explorer follows it.

We check focusable state after layout asynchronously because setFocusedNode(0)
dispatches synchronous events and callers of Document::updateLayout don't expect
DOM state changes. Also, we introduce m_didPostCheckFocusedNodeTask flag to avoid
duplicated tasks in the pending task queue.
Comment 1 Kent Tamura 2013-05-29 01:00:16 PDT 

*** This bug has been marked as a duplicate of bug 112992 ***