Potentially use UrlFilters for matching #2
Labels
No Label
Browser: Chromium
Browser: Firefox
Bug Report
Completed
Documentation
Enhancement
Feature Request
Not Implemented
Packaging
Progress Tracker
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Holllo/re-nav#2
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
If the current way of matching URLs on every
onBeforeNavigate
event proves to be too resource-intensive, one way of reducing it would be to addUrlFilter
s to theonBeforeNavigate.addListener
call.We'd have to restructure the background initialization script slightly since we'd have to also call
removeListener
whenever the user changes anything in local storage. This is easy enough withbrowser.storage.local.onChanged
though.But if the performance is fine this won't be necessary.
Possibly investigate using UrlFilters for matchingto Potentially use UrlFilters for matchingAfter testing with several hundred redirects for a while, the performance looks to be completely fine. The highest time I found for checking was 150ms and most of the time it was between 20 to 60.