Replies: 3 comments 1 reply
-
Please refer Dhruv-Techapps/acf-docs#349 |
Beta Was this translation helpful? Give feedback.
-
Hello @dharmesh-hemaram Today I tested chrome.history.onVisited.addListener() in service_worker.js and found that it can handle cases where the URL address changes. I believe we can use this to trigger Autofill again whenever the URL changes. This could allow Autofill to support Vue/ReactJS and SPA/PWA sites. From my latest tests, Autofill doesn’t seem to run when the "URL changes" via history.pushState() or history.replaceState(). |
Beta Was this translation helpful? Give feedback.
-
You can also use this method to handle URL changes, but it will track them in more detail.
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello @dharmesh-hemaram
It looks like Autofill doesn’t work on websites built with JS frameworks (e.g., Vue/React, SPA/PWA).
In cases when the screen and browser URL change via a JS router—without a full page browser refresh—or when the URL changes using history.pushState() / history.replaceState(), Autofill doesn’t re-run.
Would it be possible to handle history state changes and trigger Autofill again?
I’m not sure if you’re already using events handle like these to re-run Autofill:
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions