marco wrote:

In my own monobook I use now

if(location.href.indexOf("disable_css")==-1) {

document.write('<script type="text/javascript" src="' 
+

'http://de.wikipedia.org/w/index.php?title=Benutzer:D/monobook/user.js'

+ '&action=raw&ctype=text/javascript&dontcountme=s"></script>');
document.write('<link rel="stylesheet" type="text/css" href="'
+

'http://de.wikipedia.org/w/index.php?title=Benutzer:D/monobook/user.css'

+ '&action=raw&ctype=text/css&dontcountme=s"></link>');

}

This should be easily portable.
Marco

marco wrote:

Short:

if(location.href.indexOf("disable_css")==-1) {
...YOUR MONOBOOK...
}

Why would you want to do so? As an user, you can blank those pages or include conditional code as proposed above.

You're probably asking for it to avoid people locking to themselves but
a) You can use another skin &useskin= to avoid loading your monobook js/css
b) You can disable CSS and/or Javascript on your browser at will.

If everything fails, admins can still change that page.

It's not that the problem can't be fixed, but people not knowing the right way to do it. Adding a new parameter which only initiated know won't help on that.

What situation would require that parameter?

marco wrote:

For example if your monobook radically changes the UI but is buggy in printing. So you may want to attach that parameter so prints look just like normal. Or if you want to save pages, but want them to be saved just like normal.

For example if your monobook radically changes the UI but is buggy in printing.

Then you missed some @media screen parameters.

you want to save pages, but want them to be saved just like normal.

just delete the downloaded monobook.css