forked from gorhill/uBlock
-
-
Notifications
You must be signed in to change notification settings - Fork 193
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
Merge1.62.0 #2594
Merged
Merged
Merge1.62.0 #2594
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Allow negative integer as valid value. Related issue: gorhill#3927 Additionally, move cookie-related scriptlets/helpers into its own source code file.
Add `debug` as disposition option: if the `how` parameter is `debug`, the scriptlet will trigger a `debugger` statement and the target method won't be suppressed. Useful to find out how the method is being called by page code. To be used for investigation purpose only.
Related discussion: uBlockOrigin/uBOL-home#35 (comment) New policy setting: `rulesets` Type: array Type of array items: string Each item in the list is a list id (as seen in `rulesets/ruleset-details.json`), prefixed with either `+` to enable the ruleset, or `-` to disable the ruleset. Users will not be able to enable or disable rulesets present in the `rulesets` policy. Disabled rulesets will not appear in the dashboard. Use `-*` to remove all non-default rulesets, except for those added using `+[ruleset_id]`. Additionally, some work has been done to properly handle policy changes in a non-blocking and deferred manner, as I observed that it often takes long for calls to `storage.manage.get` to resolve. This potentailly takes care of the following issue: uBlockOrigin/uBOL-home#174
Related issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1929326 As identified by @Rob--W: https://bugzilla.mozilla.org/show_bug.cgi?id=1929326#c9 Truncated or otherwise corrupted asset content in extension storage could lead to infinite async loop causing high CPU usage in uBO and its workers. Likely related to the issue of the asset content returned as `undefined`: https://github.com/gorhill/uBlock/blob/652f1787878ba434c3a65287afcd84082c409397/src/js/cachestorage.js#L98
Related bugzilla issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1736575 The issue was fixed months ago. The removed code block is causing uBOL to be flagged as "including remotely hosted code". To be clear, the removed obsolete code block was not related to executing remote code. The referenced code was in the file itself, not remote, and this was a workaround for when Firefox was not supporting injecting script in the `MAIN` world. The issue was fixed months ago in Firefox, so there is no point for the workaround.
For example, when deserialzing from corrupted storage.
Related issue: uBlockOrigin/uBOL-home#140 This will allow more specific `removeparam` filters to override generic ones. This doesn't fix the related issue but should help more specific `removeparam` filters to be applied. Related webextensions issue: w3c/webextensions#468
Related feedback: gorhill@11ca4a3#commitcomment-149148167
Added special properties to spoof output of getBoundingClientRect().
Submission to Edge Addons store fails with: ---- The following checks failed: Package acceptance validation error: Manifest file reference 'urlhaus.full' does not exist in the zip archive. (Note: File locations are case-sensitive) Package acceptance validation error: Manifest file reference 'openphish.domains' does not exist in the zip archive. (Note: File locations are case-sensitive) ---- Guessing the use of period in ruleset file path is causing the issue.
New step: `#`, to extract the hash part of a URL. Example, URL: https://example.com/#aHR0cHM6Ly9naXRodWIuY29tL3VCbG9ja09yaWdpbi8= Filter: ||example.com^$urlskip=# -base64 As a result, navigate to https://github.com/uBlockOrigin/
Related feedback: uBlockOrigin/uBlock-issues#2531 (comment) Regression from: gorhill@9bf8d53ebe
There is no special extra steps to be taken when enabling an AdGuard lists, there is no point to have `instructionURL` for these. Related issue: uBlockOrigin/uBlock-issues#3502
As per AdGuard's documentation `/.../` is a valid matcher, to match a string argument against a regex pattern.
There is no special extra steps to be taken when enabling an AdGuard lists, there is no point to have `instructionURL` for these. Related issue: uBlockOrigin/uBlock-issues#3502
Deserialization failed to restore proper ArrayBuffer when used by multiple TypedArrays. This didn't affect uBO since this specific code path was never taken.
There is no special extra steps to be taken when enabling an AdGuard lists, there is no point to have `instructionURL` for these. Related issue: uBlockOrigin/uBlock-issues#3502
This extends coverage of strict-blocking to pattern-based filters with `doc` filter option. When proceeding with a URL-skip URL present, no temporary bypass will be created when the "Don't warn me again about this site" is left unchecked. The idea is to avoid the intermediate redirects if we navigate again on the same strict-blocked site, while a temporary bypass would prevent this. uBO's "Badware risks" list has been spinned off as its own list. The idea is that should a site be strict-blocked from that list, we would want to know the strict-block is due to the "Badware risks" list.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
also included a small improvement in the
tools/pull-assets.sh