[Webkit-unassigned] [Bug 61532] A focusedNode should be kept in each TreeScope, not in each Document.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=61532





--- Comment #2 from Dominic Cooney <dominicc at chromium.org>  2011-05-29 22:42:15 PST ---
That sounds good to me. Putting activeElement on TreeScope and having it point to the shadow host when an element in the shadow has focus sounds good.

I don’t understand why focusedNode belongs on TreeScope. Is focusedNode() the same for all TreeScopes in a document? Why does having focusedNode on TreeScope make things easier?

focusedNode is completely internal to WebKit, right? Who uses it? Why would making it non-0 when a frame is focused make things easier? Seems like it might be good to know when you’re crossing an iframe boundary.

Another question: What happens when you have this?

Document
  - <shadow-host> <--- A
    … shadow-root
      - <content>
    - <input> <--- B

Say node B has focus. Is the activeElement of the document A or B?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.