Make the fixed header optional
Open, Needs TriagePublic

Description

The fixed header might be fine as default, but hope there will be an easy way to opt out from it (without having to apply user css hacks). On a 13" I really need all the vertical screen space I can get (both articles and discussion pages tend to be long, so vertical space is precious).

sir, I am new to this community and want to start contributing . so can you assign me with an issue or bug?

I think it will be quite tricky to implement spin specific preferences, as I've never seen something like that until now.

Isarra added a subscriber: Isarra.Aug 17 2017, 5:41 PM

Skin-specific preferences are totally doable - just add them the same way as any other extension. More of an issue is when/how to display them (only show when skin is even enabled, maybe?), not cluttering up the preferences further, the age-old issue of 'should it even exist', etc.

We may want to figure out what all the potential preferences would be before adding them... or just all them all and clean it up after.

More of an issue is when/how to display them (only show when skin is even enabled, maybe?), not cluttering up the preferences further, the age-old issue of 'should it even exist', etc.

That's exactly what I meant. (Besides, I wasn't sure if skins are allowed to do that in MediaWiki).

ashley added a subscriber: ashley.Sep 13 2017, 9:58 PM

Skin-specific preferences are doable and at least one skin out there has them.

However, there has been a general push against additional preferences for various reasons, including, but not definitely limited to performance (tl,dr: more preferences = more parser cache fragmentation and whatnot). That's why I don't see this happening anytime soon and I'd argue that there really isn't a need for a preference either because we're talking about a rather essential part of the skin — kinda like what the nested navigation menu on the Nimbus skin is, for example. If you really dislike the fixed header, you can use CSS (and/or JS) to get rid of it; that's why user-specific .css and .js pages are a thing — for customizability.