[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 ship in Chrome within the next few weeks, and I imagine web developers would love it if you were to also implement. We have a basic implementation and web platform tests you may find useful [3]. Thanks, Domenic [1]: https://github.com/whatwg/html/pull/5572 [2]: https://gist.github.com/domenic/f2a0a9cb62d499bcc4d12aebd1c255ab [3]: https://chromium-review.googlesource.com/c/chromium/src/+/3456729 ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[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 at [2] 😊). So far the API has a lot of web developer enthusiasm and engagement on the issue tracker, including a polyfill [3]. We've been prototyping behind a flag in Chromium and are planning to go to origin trial soon, as we have some large sites that want to try conditionally switching out their current router code for code based on app history to see if this brings about the desired simplifications or shakes out any bugs. We also have a lot of web platform tests [4] and a mostly-complete but definitely still WIP spec [5]. We'd love to get your thoughts, whether they're a general appraisal or a more in-depth dive into the API choices and spec. I'm hopeful we can together make developers really happy with a new API for this historically-tricky problem space. Other links you may enjoy are the Mozilla standards positions issue [6] and the initial W3C TAG design review [7]. Thanks so much for your time, -Domenic [1]: https://github.com/WICG/app-history [2]: https://github.com/WICG/app-history/issues/83 [3]: https://github.com/frehner/appHistory [4]: https://github.com/web-platform-tests/wpt/tree/master/app-history [5]: https://wicg.github.io/app-history/ [6]: https://github.com/mozilla/standards-positions/issues/543 [7]: https://github.com/w3ctag/design-reviews/issues/605 ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[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 already implemented in Firefox and we're looking to ship it in Chrome soon. Would you all be interested this feature as well? It should be pretty simple to implement; it was for us at least. [2] Thanks, -Domenic [1]: https://github.com/whatwg/html/pull/1196 [2]: https://chromium-review.googlesource.com/c/chromium/src/+/3125854 ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
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 Origin-Agent-Cluster. This is due to people thinking that the "origin isolation" name implied security guarantees, like Chrome's "site isolation" term or the HTML Standard's "cross-origin isolation" term. You can read more about the reasoning at https://github.com/whatwg/html/issues/6192 and see the renaming pull request at https://github.com/whatwg/html/pull/6214. Thanks! -Domenic ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
