Jake Champion

We do not recommend using only `flags=always` - it will cause issues. If wanting to always serve polyfills, we highly recommend using it in combination with `gated` like so, `flags=always,gated`,...

Could you please explain what is incorrect, it looks correct to me

According to the documentation, there isn't a way to do this. I would also imagine that pressing enter would submit the form, not move to the next input field.

@gobengo Do you have a reference to the fact about Github refusing to implement module support? I was about to start work on creating a fetch polyfill which didn't shim...

Heads up: You might get a performance hit if the virtual nodelist is large, unless you are using transferrable objects or SharedArrayBuffers. This seems to say the opposite though: https://nolanlawson.com/2016/02/29/high-performance-web-worker-messages/

You are correct in that assumption, this library is OS agnostic in nature On Sun, Dec 22, 2013 at 9:08 PM, daedeloth [email protected] wrote: > Hi, > > Awesome project!...

If you could test it in the latest nightly as to see if it was a fault on Mozilla's behalf that would be great. If it isn't, could you send...

It is still an issue: ``` console.log(Object.getOwnPropertySymbols(Object.prototype).length) // 11 (All the built-in Symbols) Symbol('12') console.log(Object.getOwnPropertySymbols(Object.prototype).length) // 12 Symbol.for('13') console.log(Object.getOwnPropertySymbols(Object.prototype).length) // 13 ```

> What's the right thing to do if we don't support the version? Panic? If so, we could maybe put it into the `fsthttp.ServeFunc` function since that's going to be...

Yes it was, thanks for re-opening this