PhistucK
PhistucK
I think this is needed. The current way of blocking a `history.pushState` (or clicking on the browser back button after a `history.pushState`) navigation is extremely hacky (re-pushing the previous navigation)...
Or similar to the `fetch` event of service workers, `event.waitUntil(promise)`.
See https://github.com/supasate/connected-react-router/pull/438 for a temporary fix. I am not sure it is the correct/performant way to support the new React Router v6-beta.0, but it works.
@Whazor - hmmm, how is that different (it is already an object)? Unless I am blind, you just removed two line breaks...
@annevk - it seems to just be missing a `new` (`new event.constructor(event.type, event);`).
@LeaVerou - plus, having an event listener does not mean it supports keyboard shortcuts. `accesskey` exists for a declarative way.
@ebidel and @loonybear - those percentages are feeding investigations and decisions on Blink intents, can a fix be merged, or can something else be done so that the numbers would...
@ebidel - having a few metrics above 100% looks like the tip of the iceberg and makes me (at least) not trust the rest of the results. Other things might...
> The way to solve this would be Tracking State then your rewrite should also version the rewrited assets example image.jpg?md5hash this way you can invalidate the cache of the...
F. seems the most effective, combined with when containers are created/used, you can score a pretty accurate view. D. would also be cool, but you will probably have to offer...