- From: Dave Tapuska via GitHub <sysbot+gh@w3.org>
- Date: Mon, 06 Mar 2017 20:45:37 +0000
- To: public-css-archive@w3.org
Let me clarify. I've removed my Edge comment that it is strange; it actually makes the most sense provided we can actually compute these values from the hit test. Seems https://trac.webkit.org/changeset/82225 was the original change that introduced this behavior. And ultimately I think `if (m_target == target) ` would have fixed the problem with the O(n^2) vs O(n) that the change was trying to address. Chromium/WebKit reset the cached bool whenever the target changes for an event. Now a target is a readonly attribute so javascript can't set it although I believe the target changes when going into a shadow dom. So it could be possible that reading the cached value changes across the shadow DOM exhibits the "live" behavior FireFox has. So granted it isn't as simple as determining it at hit testing time because the values depend on the target and the target might change across the shadow dom, right? -- GitHub Notification of comment by dtapuska Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1070#issuecomment-284526634 using your GitHub account
Received on Monday, 6 March 2017 20:45:43 UTC