User Details
- User Since
- Jul 12 2020, 3:57 AM (282 w, 4 d)
- Availability
- Available
- LDAP User
- Unknown
- MediaWiki User
- HonestCandidate [ Global Accounts ]
Apr 13 2022
@alexhollender_WMF did you happen to think about perhaps having a tabbed approach where you can have either the ToC or editor tools open and perhaps that van persist across pages? I know there is an extra layer of complexity when dealing with toggling and remembering what a preference is (user preferences perhaps, I don't know) but it could enable people to have a preferred menu type open (by default perhaps), retain the familiarity for editors of where the tools are and best of all, not have to squeeze the content <- as that is precisely what they would want to be interacting with anyway, right?
@Jdrewniak Where can one get this Chrome extension for testing?
@ovasileva I hope these dump files do work because it would be amazing to use these when developing new skins.
@Jdlrobson I think expired or invalid query parameters usually can potentially break things with a bad URI but it is up to the server that receives it. Perhaps a rewrite condition can be created somewhere but that is outside of my domain.
I'm surprised this is only a Medium, but then again how many people indeed print from mobile? Do you happen to have numbers on that? (Just curious!) @LGoto
@Jdlrobson How long will the classes be held in html caches? Are you having to do those weird 2 phase deployments where the class is retained but then updated and cleared based on regional traffic?
@cjming the patch looks good and the improvements are noticeable. I do think the horizontal alignment for both sidebar and ToC. LGTM!
@alexhollender_WMF I agree with the thought that it should match the text. I would think about how this will affect something like a potential dark mode in the future but if the templates have a color variable, it would be super easy to match the text and thus always map to that variable (or css class) name,
Jan 26 2021
@Jdlrobson Right at 1042px window width, the content goes behind the open sidebar and the margin-left: 11.5em is no longer active. The correct placement of the content kicks in ~1156px window width. So that means there's a 114px discrepancy possibly within the @media query in the css (if there indeed is one) affecting when that 11.5em left margin is deactivated.
@ovasileva @Jdlrobson I believe it is because the current preferences schema mostly has a few booleans to signify individual preference choices. If the schema has any little-used/outdated keys in the object, perhaps you can repurpose one to essentially serve as 'DIP-opt-in'
