Skip to content
This repository was archived by the owner on Nov 6, 2023. It is now read-only.

Remove match_rule and f attributes. - #3883

Merged
semenko merged 4 commits into
EFForg:masterfrom
jsha:no-match-rule
Jan 15, 2016
Merged

Remove match_rule and f attributes.#3883
semenko merged 4 commits into
EFForg:masterfrom
jsha:no-match-rule

Conversation

@jsha

@jsha jsha commented Jan 14, 2016

Copy link
Copy Markdown
Member

They're no longer used.

cc @semenko for review.

jsha added 3 commits January 13, 2016 23:29
This eliminates "moot" as a special category, and treats all rulesets that have
a matching target host but are disabled as "inactive" in the applicable rules
list, allowing us to eliminate a chunk of regex work in wouldMatch.
@semenko

semenko commented Jan 14, 2016

Copy link
Copy Markdown
Contributor

Good call! Cursory LGTM -- I'll test this more over the ~weekend.

@blockoperation had a lot of related changes (#1775) for inspiration at https://github.com/blockoperation/https-everywhere/commits/chromium-memory-usage-v2

@semenko semenko added the chrome label Jan 14, 2016
@semenko semenko self-assigned this Jan 14, 2016

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please rm skin/tick-moot.png

@semenko

semenko commented Jan 14, 2016

Copy link
Copy Markdown
Contributor

Ok, just a few outstanding moot references to clean up:

chrome/content/code/AndroidUI.jsm
chrome/skin/https-everywhere.css
chrome/skin/tick-moot.png

@jsha

jsha commented Jan 15, 2016

Copy link
Copy Markdown
Member Author

Fixed the issues you mentioned. Thanks!

@semenko

semenko commented Jan 15, 2016

Copy link
Copy Markdown
Contributor

😆 lingering moots

semenko added a commit that referenced this pull request Jan 15, 2016
Remove match_rule and f attributes.
@semenko
semenko merged commit ca4e86e into EFForg:master Jan 15, 2016
jsha added a commit to jsha/https-everywhere that referenced this pull request Jan 20, 2016
This caused a regression: Rules that are active but not taking effect (formerly
moot rules) are simply not listed, when my intention was to list them (i.e.,
match the Chrome behavior).

Will roll forward again when I have a fix, but didn't want to leave things in a
broken state until then.
jsha added a commit to jsha/https-everywhere that referenced this pull request Jan 20, 2016
This caused a regression: Rules that are active but not taking effect (formerly
moot rules) are simply not listed, when my intention was to list them (i.e.,
match the Chrome behavior).

Will roll forward again when I have a fix, but didn't want to leave things in a
broken state until then.

This is a partial revert because the Chrome changes were fine, so I'm leaving
them.
semenko added a commit that referenced this pull request Jan 20, 2016
Hainish pushed a commit that referenced this pull request Jan 26, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants