-
Notifications
You must be signed in to change notification settings - Fork 77
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
uBlock disable fixes a problem that whitelisting site will not -- why? #119
Comments
Fill the entire template instead of leaving it empty. |
I read the issue and nowhere does it mention consulting the logger -- a required step to rule out filter issues. Also, I fail to see how the provided screenshot is of any help. |
Volunteers can't help people un-willing to be helped and contribute back to help solve issues for all: long unproductive post with no sign of following the advice to look at the logger as first step.
"Filter issues" implicitly include custom filters and rules. The logger is key. Anyway, from this point on I will consider only information provided here, the posts on Pale contain nothing actionable. |
First he files a bug without filling required info, asks us to answer him on his choice of 3rd party forum as if we offer such service for him, when asked here to fill in bug report, ignores that purposefully and responds to that on that 3rd party forum, displaying his sense of entitlement. These are the kind of posters who I feel don't deserve any help from this tracker. He posted it there, so he should expect any help there itself. |
And yet that firefox-legacy branch (which point is to keep supporting more than just Pale Moon, i.e. Sea Monkey et al.) has more activity than ABPrime, and support modern filtering capabilities such as As I already said regarding the firefox-legacy branch, pull requests crafted with care are welcomed, so are positive contributions (example). Stating "isn't a very good Pale Moon extension" isn't a positive contribution, it's un-actionable.
@lakrsrool checked the "This is not a support issue or a question" item. The issue tracker is for actual issues with uBO. The idea is to not over-burden volunteers, and the rules in place are to protect the project from being run in the ground by over-burdening volunteers -- there is no "staff" here, just volunteers. Consider the amount of invalid issues being opened despite these rules, so relaxing them is not going to help, the rules just force people to be more thorough on their side before opening issues, and as a result spread the workload of validating real issues to more people. Thousands of issues have been dealt with since the project was first released, and this is your presence in the issue tracker, so for you to lecture how things should work here is a bit much. |
Please refer to this forum topic for questions I have in regards to issue title:
https://forum.palemoon.org/viewtopic.php?f=46&t=19615
Thanks
Prerequisites
Description
[Description of the bug or feature]
A specific URL where the issue occurs
[A specific URL is MANDATORY for issue happening on a web page, even if it happens "everywhere"]
Steps to Reproduce
Expected behavior:
[What you expected to happen]
Actual behavior:
[What actually happened]
Your environment
The text was updated successfully, but these errors were encountered: