[webkit-dev] Request for position on import.meta.resolve()

Hi webkit-dev, We're proposing a small additional function to add to the HTML Standard, named import.meta.resolve(). See the PR [1] and a mini-explainer [2]. Gecko folks have reviewed the PR and contributed to the discussion, but any thoughts from WebKit would be very welcome. We're hoping to

[webkit-dev] Request for position on app history API

Hi webkit-dev, The Chrome team, with some help from Mozilla folks, have been working on a proposal for a new history/navigation API aimed specifically at the needs of single-page apps. The current name is the "app history API". You can see the explainer at [1] (and the name bikeshedding thread

[webkit-dev] Request for position on self.reportError()

Hi webkit-dev, We recently added a small utility function, self.reportError(), to the HTML Standard [1]. It is pretty simple and just lets developers appropriately send errors to the "error" event handler and the console, like what happens when the browser reports uncaught exceptions. This is

Re: [webkit-dev] Request for position on the Origin-Isolation header

Hi again webkit-dev, I'm just pinging this thread to let you know that in the HTML Standard repository (and Chrome implementation), we're working to rename this feature from "origin isolation" to "origin-keyed agent clusters", with the header going from Origin-Isolation to

Re: [webkit-dev] Request for position on import maps

Thanks for your response Ryosuke! From: Ryosuke Niwa > How does this feature supposed to work with CSP subresource integrity? >As far as I've read various specs and the proposal, it's not currently >possible to specify any integrity checks on modules loaded via import this. >This is a pretty

[webkit-dev] Request for position on import maps

Hello webkit-dev, For the last couple of years myself some other Chrome folks have been working on the import maps proposal. This allows controlling the behavior of JavaScript import statements and import() expressions, in particular by allowing the page to customize the translation of the

Re: [webkit-dev] Request for position on the Origin-Isolation header

Thanks Ryosuke! From: Anne van Kesteren > On Fri, Aug 21, 2020 at 2:41 AM Ryosuke Niwa wrote: >> I feel like I saw some discussions of also differentiating based on >> protocol (treating http://webkit.org and https://webkit.org >> differently). Do you know you've already had such a

[webkit-dev] Request for position on the Origin-Isolation header

Hello webkit-dev, I've been working on a new header called Origin-Isolation, which is a way of allowing origins to opt-out of using document.domain and cross-origin sharing of WebAssembly.Module, and thus allowing the browser to put them into an origin-keyed agent cluster instead of a