Last modified: 2012-06-21 02:00:36 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T37063, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 35063 - Implement a front-end for interacting with resourceLoaderDebug cookie
Implement a front-end for interacting with resourceLoaderDebug cookie
Status: NEW
Product: MediaWiki
Classification: Unclassified
JavaScript (Other open bugs)
1.17.x
All All
: Low enhancement (vote)
: Future release
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-03-08 11:43 UTC by Krinkle
Modified: 2012-06-21 02:00 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Krinkle 2012-03-08 11:43:17 UTC
* If debug=true, remember in session
* the "set debugmode" code should check session in addition to GET query param
* going to debug=false will also unset it in the session

Allows to navigate the wiki, submit forms (bug 35061), and stuff.

To prevent users from unknowingly staying in debug mode, JS should but up an informational notification on the page informing something short like: "You've enabled debug mode of client resources delivery, click here to disable this"
Comment 1 Michael M. 2012-03-09 08:58:41 UTC
Since setting a cookie "resourceLoaderDebug" enables debug mode, this probably can be done easily on client side.
Comment 2 Krinkle 2012-03-09 12:17:50 UTC
(In reply to comment #1)
> Since setting a cookie "resourceLoaderDebug" enables debug mode, this probably
> can be done easily on client side.

The cookie can be set on the client side, however the initial server request needs to know this before any client code is processed because it influences how the page is rendered very early on. (one could implement a redirect/refresh, but that gives the same problem with form submissions).

This needs (at least some) server development. But that's OK, it's not a hard thing to do :), just other priorities right now (although patches are welcome at any time :)
Comment 3 Krinkle 2012-06-21 01:59:06 UTC
(In reply to comment #1)
> Since setting a cookie "resourceLoaderDebug" enables debug mode, this probably
> can be done easily on client side.

Ah, this is already implemented. I didn't know that. (bug 25610 slipped by silently, and it never made it into documentation).

Repurposing this bug for the GUI module.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links