Repository navigation
Script resources requesting blocks entire extension #894
Description
Like my latest comment on this old issue:
The update check effectively prevents the entire extension from functioning properly, including loading/responsiveness of other extension interfaces, and all script injection processes etc.
In other words, if there is difficulty in obtaining resources due to any network issues, the entire extension will be suspended and will not work before the 30 second hard timeout, and no scripts will be injected into the page during this time.
This can be a serious and frustrating problem for users. And recently some users also reported this in the App Store Review.
In fact, after the above comment were post, I have begun to investigate and redesign the native messaging framework in the back-end reconstruction, eliminating blocking and make heavy tasks asynchronous, in order to completely solve related issues. But it still takes time.
Before the release of v5.0, we should try to improve the user experience of version 4.x.x.
My opinion is to temporarily disable automatic script update checking in v4.x.x. Although users will still encounter the issue when checking manually, at least this is an effective mitigation measure for most daily use scenarios.
In fact, v5.0 beta has already disabled automatic checking by default and has a related interval setting, but users cannot easily do this in v4.x.x.
@quoid What do you think?
Activity
quoid commentedon Dec 26, 2025
I think that temporarily switching from automatic to manual update checks sounds like a good idea.
ACTCD commentedon Dec 26, 2025
Ok, then I will do it and release a new version ASAP.
[-]Update check blocks entire extension[/-][+]Script resources requesting blocks entire extension[/+]ACTCD commentedon Dec 27, 2025
We have disabled automatic scripts update checks in v4.x.x, which should alleviate most of the blocking scenarios that users may encounter.
However, this did not fundamentally solve the issue.
In fact, the same issue may be triggered if a user installs/saves a script that contains a new
@requireresource that is hard to get. Although these may be edge cases, they have indeed existed for years. There is no easy solution other than refactoring, so it will incorporated into the 5.0 work.