You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add option to disable addon on current domain #509
When this addon breaks someone's workflow it would be extremely important to have the option to just disable it for a domain, so as to not having to wait till a fix is in.
I think this should be handled separately from #510
The Claude issue looks like a correctness bug in fragment parsing/serialization and should be fixed directly. This issue, though, is still valid as a broader resilience feature: when ClearURLs breaks a workflow on a specific site, users need a fast way to disable it there without turning the addon off globally.
My plan is to treat this as a separate feature PR:
add a persisted per-site/domain disable list
expose it in the popup as something like Disable on this site
short-circuit request cleaning for disabled sites
That way the bugfix can ship independently, and this feature still provides an escape hatch for future site-specific breakage.
How about also adding an option to enable cleaning only for a specific list of sites?
I find that ClearURLs break several of the sites I use, but I actually only need the URLs cleaned from a small subset of websites. For my use case, it would be much simpler to specify which sites I want to use ClearUrls on than to disable it for all the sites I don't need it for.
When this addon breaks someone's workflow it would be extremely important to have the option to just disable it for a domain, so as to not having to wait till a fix is in.