Thanks for the detailed explanation.
The only thing I'm not sure I understand is the pattern you described:
```
HTMLElement.prototype.foo = HTMLElement.prototype._foo;
```
I had this pattern in mind when you talked about prollyfills:
```
HTMLElement.prototype._foo = function() {
if
+domenic
We've recently finished the ReadableStream part of the spec and
experimenting integration with the Fetch API. Most of the spec is still
unstable. I don't have bandwidth to maintain W3C version of the spec even
briefly currently...
Takeshi
On Tue, Aug 4, 2015 at 11:13 PM, Arthur Barstow
Would implementors want to support (writing stuff to the clipboard)?
Actually, no - The Simpsons already did it.
Lets not think about windows clipboard. Those are Windows.
We are browser.
I feel clipboard is something that contains copy of
contenteditable items of the same web page.
We seem to
Do polyfills like WebReflection's DOM4 look promising?
No. Lets choose to not spoil a text-based markup language by trying to
emulate geometry. etc. There are other tools for geometry. HTML not suited
for geometry.
'I feel it's more sustainable to bet on spec APIs.'
No. I prefer lets Focus on
