Philip Jägenstedt

Results 1054 comments of Philip Jägenstedt

Thanks for the pointers, I'll have to revert https://foolip.github.io/spec-reactions/ to before I hacked around the problem and see if your suggestions work.

Oh, I guess some of the tests pass for the wrong reasons?

Thank you @mosaadm! It looks like the path data in all of the files are the same now, so I'll go ahead and merge this.

We're figuring this out as we go, but basically the issue should be turned into one or more browser engine bugs, or sometimes spec bugs. How to communicate back any...

@mstensho might you be able to help triage this issue, to figure out which browser or spec bugs this is about?

I think that as written the spec doesn't allow `[SameObject]` for `FrozenArray` but that seems unlikely to be intentional. A spec issue sounds good.

I came to file an issue suggesting this and found this PR, after noticing the somewhat unusual arrangement in https://github.com/web-platform-tests/wpt/pull/12390#pullrequestreview-145055495. @romandev, will you be able to pick this up again?

I came here to file this issue, but I'd like to go further. Probably the most problematic aspect is the ability to `document.write()...` which is parser-blocking and thus blocks the...

@jakearchibald I see, glad to hear you were also shooting for the same thing! Trying to figure out what the most surgical restriction of bad `document.write` behavior would be I...

@clelland, looking at https://github.com/w3c/webappsec-feature-policy/blob/master/policies/document-write.md, I wonder if some of that isn't more about `sync-script` than `document-write`. It says: > anti-pattern, parser-blocking JavaScript API However, is the parser-blocking behavior not covered...