You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Meant to open this a little while ago, but it seems as of the latest version of Chrome (109) the technique we use for Chromium browser based event delegation isn't working anymore.
For example, if you go to the About page, and then go the Docs page, you can see the docs site is doing a full page reload.
Still working in Firefox though! 😅 🦊
Details
So doing some logging in the browser, I am definitely not seeing path in the logged event object, so that obviously explains why its not working anymore.
I suppose this puts Chrome in the same situation as Safari now without access to path or originalTarget` (Firefox) so not sure if this means we have to figure out #559 right now then?
Will see if there is a quick win here though, or maybe a slight tweak to our event delegation implementation?
I suppose this is worth a shout to anyone reading this who might be interested in helping with #560 🙏
The text was updated successfully, but these errors were encountered:
thescientist13
changed the title
static router not working on Chrome (anymore)
static router not working on Chrome / Edge browsers (anymore)
Feb 16, 2023
This StackOverflow thread covers the exact issue in question I think, with some of the comments to the top level reply calling out similar techniques in our current router implementation.
I suppose this may just be an issue with closed shadow roots in general maybe? It seems a lot to open all ShadowRoots just for classic event delegation? 🤔
Type of Change
Bug
Summary
Meant to open this a little while ago, but it seems as of the latest version of Chrome (109) the technique we use for Chromium browser based event delegation isn't working anymore.
For example, if you go to the About page, and then go the Docs page, you can see the docs site is doing a full page reload.
Still working in Firefox though! 😅 🦊
Details
So doing some logging in the browser, I am definitely not seeing
path
in the logged event object, so that obviously explains why its not working anymore.I suppose this puts Chrome in the same situation as Safari now without access to
path
or originalTarget` (Firefox) so not sure if this means we have to figure out #559 right now then?Will see if there is a quick win here though, or maybe a slight tweak to our event delegation implementation?
The text was updated successfully, but these errors were encountered: