Intent to Implement and Ship: Node.isConnected

[Yuzu Saijo]

Contact emails

yu...@chromium.org, yu...@google.com

Spec

https://dom.spec.whatwg.org/#dom-node-isconnected

Summary

The isConnected attribute’s getter returns true, if context object is in a shadow-including document, and false otherwise.

Motivation

Web developers want a mechanism to tell if an element in a ShadowRoot has been inserted into the Document. 

See the discussion here: https://github.com/w3c/webcomponents/issues/81

Interoperability and Compatibility Risk

There is no risk of compatibility.

OWP launch tracking bug

https://bugs.chromium.org/p/chromium/issues/detail?id=599743&can=2&start=0&num=100&q=yuzus&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified&groupby=&sort=

Link to entry on the feature dashboard

https://www.chromestatus.com/features/5676110549352448

Requesting approval to ship?

Yes.

[Boris Zbarsky]

On 4/4/16 3:50 AM, 'Yuzu Saijo' via blink-dev wrote:
> Interoperability and Compatibility Risk
>
> There is no risk of compatibility.

As in, you're 100% sure no page uses this identifier at global scope
from event handlers, say? I notice this new attribute is not
[Unscopable]....

-Boris

[Hayato Ito]

Per the discussion, https://github.com/w3c/webcomponents/issues/81, 

the current conclusion is to leave out [Unscopable], as we did it in Node.rootNode too.

[Philip Jägenstedt]

LGTM1

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.

[Chris Harrelson]

LGTM2

[Dimitri Glazkov]

LGTM3.

:DG<