-
-
Notifications
You must be signed in to change notification settings - Fork 386
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
Disqus Comment Widget Replacement #2613
Conversation
This comment has been minimized.
This comment has been minimized.
073d2d4
to
bfa6f37
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
2c44201
to
ef54d9e
Compare
dd36209
to
45d98e0
Compare
45d98e0
to
a6044cb
Compare
@ghostwords the latest commit applies the simplification we spoke about in the developer call earlier today. I also added the wildcard support to |
2bc604a
to
9246104
Compare
Rebased with |
No need for regexes yet.
- If there are multiple wildcard domain matches, make sure all of them were blocked - If we have a wildcard domain that didn't match our criteria, don't keep going onto non-wildcard domain logic
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good generally. Thank you!
I'll do some more testing with my followup commits tomorrow.
Domain matching for widget elements created after initial page load needed to be updated to support wildcards.
This replaces the previous PR #2271 with one that's more up-to-date from master's current state.