Luke Warlow

Chrome intent to ship: https://groups.google.com/a/chromium.org/g/blink-dev/c/jM5au7yYzHM/m/L8r7x5CmAAAJ

Just as an fyi this has been merged into the html spec and shipped in ~~chromium 120~~

This has gone through some iteration in the spec and chrome implementation to handle some edge cases better. As a result it should be even more stable to implement in...

> Apart from that, it also seems concerning that the current draft reportedly lacks features Chromium has implemented (per https://github.com/mozilla/standards-positions/issues/20#issuecomment-1853427823) and apparently also has features that are not being implemented?...

Wrt to the CSP integration I can see value in a potential `trusted-eval` (name tbd) expression to replace `unsafe-eval`. This new value along with the existing trusted types directives could...

It would behave as if you have strict csp without unsafe-eval today. I believe there'd discussions surrounding the eval csp aspect elsewhere so I'll leave a comment there. Though that...

https://github.com/mozilla/standards-positions/issues/794 Here's a link to the Mozilla Position Issue

Mozilla have declared their position as supportive as an FYI

https://www.w3.org/TR/2023/WD-css-anchor-position-1-20230629/ this now has a first public working draft as an fyi

One possible fix for this would be to race the promise against a setTimeout so you can reject and move on. ``` function expectMessage(filter) { return Promise.race([ new Promise(resolve =>...