When opening the DOM inspector of Firebug, MediaWiki's JavaScript assumes deprecated properties and methods are accessed (they probably are by Firebug) and sends a whole bunch of log messages. Since this takes, depending on whether they are sent to event.gif, usually about 10s per view of the properties tab, it makes web-developement with Firebug essentially ineffective and slow. I don't like the new built in Firefox debugging tools; they feel like made for touch devices (no context menus) and suffer from other serve usability issues. Also I am not sure I can trust them; one day I was finding them showing wrong stack traces and variable values that were simply not correct. Is there a way to turn off deprecation logging?
Description
Details
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
resourceloader: Log each deprecation only once from mw.log.deprecate | mediawiki/core | master | +33 -4 |
Related Objects
- Duplicates Merged Here
- T103962: Do not repeat deprecation warning in JavaScript console
Event Timeline
Similar issue affects IE11's development tools too. Personally I think it's a bug in the tools, not in MediaWiki.
Indeed, it is. However, it's just making JS fiddling with MediaWiki no fun. Perhaps we could limit the printed deprecation warnings (I think the request to event.gif or printing the stack trace is the really slow part) to 3 per page view in non-debug mode or have a simple switch to turn them off?
Change 268466 had a related patch set uploaded (by PlasmaPower):
Only log deprecations once
Change 268466 abandoned by PlasmaPower:
resourceloader: Log each deprecation only once from mw.log.deprecate
Reason:
I'm not sure this is a solvable problem, at least not easily.
Change 268466 restored by Krinkle:
resourceloader: Log each deprecation only once from mw.log.deprecate
Change 268466 merged by jenkins-bot:
resourceloader: Log each deprecation only once from mw.log.deprecate