Trey Shugart

Browsers seem to consistently report outerHTML / innerHTML between vendors but have odd behaviour when inspecting the values. For example: ```js const div = document.createElement('div'); div.innerHTML = '"test1 & test2"';...

Originally reported in https://github.com/skatejs/web-components/issues/11 and related to https://github.com/ariya/phantomjs/issues/13895. To test in phantom run: 1. `npm install karma-phantomjs-launcher` 2. `sk-tests --browsers PhantomJS`

See: https://github.com/webcomponents/webcomponentsjs/blob/3ea23df8bc0f45d44fc903b706d379d7d50aba29/src/ShadowDOM/wrappers/HTMLElement.js#L154. I found this from this comment: https://github.com/webcomponents/webcomponentsjs/issues/511#issuecomment-238486248. It seems that we should be able to use a similar algorithm to the one in the first link instead of...

There's not really a use case for it yet and it creates issues when trying to share code as we'd have to pass around the user defined tag name.

Do not slot empty or whitespace-only text nodes.

3

I don't want to have to do this, but I don't know of a good algorithm to determine if whitespace should be part of a slot. The problem comes when...

Currently if you set `innerHTML` to a `` and you specify special table elements, they'll be wrapped in a `` due to https://github.com/skatejs/named-slots/pull/46 which is a necessary fix for ``...

Add activeElement property to shadow root.

1

Shadow roots should contain an active element for accessibility. See http://w3c.github.io/webcomponents/spec/shadow/#active-element.