Closed Bug 1011403 Opened 11 years ago Closed 11 years ago

Suppression of internal javascript warnings

Categories

(DevTools :: Console, defect)

Product:
DevTools
Component:
Console
Version:
29 Branch
Platform:
x86_64
All
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: marvin.froehlich, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release) Build ID: 2014042500 Steps to reproduce: The Javascript console (CTRL+K) shows an internal warning for every single main request. There should be a way to suppress those, since these bugs come from internal FF scripting and are usually not fixed in the next release. The current warning is as follows (in german): getUserData() und setUserData() sollten nicht mehr verwendet werden. Verwenden Sie stattdessen WeakMap oder element.dataset.
OS: Linux → All
Component: Untriaged → Developer Tools: Console
On the contrary, when we see such warnings we try to fix them if possible. Which pages do you get this on? For example I tried opening the Firefox 29.0.1 web console in this page and I couldn't see any warnings.
I see this literally on every single page, where ever it comes from. I have configured my console (CTRL+K) to display Net (Errors, Warnings, Logs), JS (Errors, Warnings), Log (Errors Warnings, Information, Log). Maybe it has something to do with this configuration. I do agree, that no Firefox developer should ever disable any of these messages, so that they get a chance to see and fix them. But since it is a very internal message, it is of no value for us users and just floods the logs of us web devs.
The message disappears, if I hide JS warnings. But of course I want to see my own JS warnings.
Do you have any add-ons installed? Could you try with add-ons disabled or in a clean profile?
That helped. It is AdBlockPlus, that produces this warning. I still think though, that there should be a switch to hide warnings from AddOns. Yes, I agree, that these messages must be seen. But if I develop or test an AddOn, I simply should not use this switch. What do you think?
I think the most useful thing to do here is to contact the add-on authors and tell them that getUserData/setUserData are deprecated and point them to this page: https://developer.mozilla.org/docs/Web/API/Node.getUserData As a feature request, I find a switch to hide warnings from the special category of add-ons that add content globals to be of dubious utility - in general, warnings from add-ons appear in the Browser Console (Ctrl-Shift-J) because they come from a chrome-privileged global. It is true that it could be useful to some people, but every additional mode switch comes at a non-negligible maintenance cost and in this case the benefits don't outweigh the costs in my view.
Looks like the issue is already fixed. https://issues.adblockplus.org/ticket/47 And according to that discussion it was not fixed for such a long time, because it was a Firefox bug. Thanks for taking the time and being fair, Panos.
Thanks for the pointer, I didn't know about that WeakMap bug. Resolving, as ABP has now fixed this warning.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.