Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

workaround for people struggling with throttling #62

Closed
wants to merge 1 commit into from

Conversation

divinity76
Copy link

For me, even the "track changes" button updates too slowly to be useful while developing, where I often make a small change, save, and refresh the page in a matter of seconds.

Found a workaround.

For me, even the "track changes" button updates too slowly to be useful while developing,
where I often make a small change, save, and refresh the page in a matter of seconds.

Found a workaround.
@tophf
Copy link
Member

tophf commented Oct 14, 2024

I wouldn't recommend this method in general because it requires allowing file access to the extension, which exposes the entire file system to any userscript. In modern Chrome the preferred method of tracking is to drag the file into any Violentmonkey UI without allowing file access to the extension.

Note that in modern Chrome Violentmonkey can track the files without any delay/throttling if you enable chrome://flags/#enable-experimental-web-platform-features. I'll add this info to the documentation.

@tophf tophf closed this Oct 14, 2024
@tophf
Copy link
Member

tophf commented Oct 15, 2024

I'm open to adding a variant of your method with localhost URL, not file:, and mentioning that it'll work only for scripts that don't require the tab to be reloaded.

@divinity76
Copy link
Author

@tophf I think you should go for it. It can be a serious problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants