Document "Error Console" and the need to "Allow" ABE sites
Posted: Sat Nov 14, 2015 6:33 am
https://noscript.net/abe/users.html states that "Whenever a certain rule is matched, a message is logged in the browser's Error Console".
For a great many people, the console they are familiar with is the one in the developer tools available via F12 (either Firebug, or the suite which is nowadays built-in), and it's entirely unclear that those consoles are useless for seeing ABE messages!
Furthermore, even if you do open the required console with Ctrl-Shift-J, it *looks* identical to the console in the built-in developer tools, so one might even presume that they were simply different ways of viewing the same things, and not even test it. (I did test it, but I was certainly surprised to see the difference.)
This is very confusing when you are trying to learn how ABE works, and nothing you try produces any apparent log message. It would be very beneficial if you could update https://noscript.net/abe/users.html to explain both (a) that you get to the error console with either Ctrl-Shift-J or via the Tools -> Web Developer -> Browser Console menu items; and (b) that you MUST use this particular console, because other consoles will NOT show the messages in question.
The second critical point which could really use some highlighting on that page is the fact that ABE rules take second place to the normal NoScript blocking, and that you therefore must first "Allow" any Site covered by an ABE rule before that ABE rule will be processed.
Thanks!
For a great many people, the console they are familiar with is the one in the developer tools available via F12 (either Firebug, or the suite which is nowadays built-in), and it's entirely unclear that those consoles are useless for seeing ABE messages!
Furthermore, even if you do open the required console with Ctrl-Shift-J, it *looks* identical to the console in the built-in developer tools, so one might even presume that they were simply different ways of viewing the same things, and not even test it. (I did test it, but I was certainly surprised to see the difference.)
This is very confusing when you are trying to learn how ABE works, and nothing you try produces any apparent log message. It would be very beneficial if you could update https://noscript.net/abe/users.html to explain both (a) that you get to the error console with either Ctrl-Shift-J or via the Tools -> Web Developer -> Browser Console menu items; and (b) that you MUST use this particular console, because other consoles will NOT show the messages in question.
The second critical point which could really use some highlighting on that page is the fact that ABE rules take second place to the normal NoScript blocking, and that you therefore must first "Allow" any Site covered by an ABE rule before that ABE rule will be processed.
Thanks!