[FIXED] 11.0.44rc cs order problem
Posted: Sat Sep 12, 2020 8:39 am
A weird one that took too much of my time.
Sometimes (very rarely) the SyncFetchPolicy fails to run on the page (both FF 80 & 81). Could not figure a surefire way to reproduce, but here are the steps that might manifest it:
- Open any page.
- Reload and/or navigate to about:newtab and back. (Maybe necessary or not?)
- Wait for 5 minutes or more. (Important step!)
- Navigate to about:newtab and back.
- Observe SyncFetchPolicy failing to run.
If the above works once, it happens reliably after every 5+ min wait until the tab is closed. If not, closing and reloading tab/browser/NoScript might be what it takes. But it can be hard to get it into the right state. Whatever that might be. Also no idea where the ~5 min cutoff comes from. Simply determined by trial and error.
The clear underlaying reason for the SyncFetchPolicy failing to run is that the SyncFetchPolicy.js and DocumentFreezer.js are run after the other contentscripts.
The docs do state the contentscripts are run in the order they appear in the array, but there is no mentioning how multiple arrays are handled. So not sure if bug or not, but fallback is needed in case this might happen on other circumstances.
Sometimes (very rarely) the SyncFetchPolicy fails to run on the page (both FF 80 & 81). Could not figure a surefire way to reproduce, but here are the steps that might manifest it:
- Open any page.
- Reload and/or navigate to about:newtab and back. (Maybe necessary or not?)
- Wait for 5 minutes or more. (Important step!)
- Navigate to about:newtab and back.
- Observe SyncFetchPolicy failing to run.
If the above works once, it happens reliably after every 5+ min wait until the tab is closed. If not, closing and reloading tab/browser/NoScript might be what it takes. But it can be hard to get it into the right state. Whatever that might be. Also no idea where the ~5 min cutoff comes from. Simply determined by trial and error.
The clear underlaying reason for the SyncFetchPolicy failing to run is that the SyncFetchPolicy.js and DocumentFreezer.js are run after the other contentscripts.
The docs do state the contentscripts are run in the order they appear in the array, but there is no mentioning how multiple arrays are handled. So not sure if bug or not, but fallback is needed in case this might happen on other circumstances.