https://bugzilla.wikimedia.org/show_bug.cgi?id=70351
--- Comment #25 from Isarra <[email protected]> --- (In reply to Matthew Flaschen from comment #24) > (In reply to Isarra from comment #22) > > In this case that the skin-specific styles now at least can be disabled is > > an improvement, but that is still backwards: they shouldn't be enabled at > > all unless the skin specifically wants them. > > For the time being, it's not a skin-specific style. > > > having nothing by default really is the best solution at present. > > That's your opinion. No other skin writers have expressed that opinion, as > far as I know. Jack Phoenix (who probably holds the record on number of skins created and maintained) agrees; he just gave up on trying to argue with people about skin-related things long ago because nobody ever listens. I keep trying, because I'm insane. Also it actually has gotten better more recently, but only kind of. > > If I had a working framework for styling form elements, I could probably > > create some mocks of a more generic set of default styles, but as is I don't > > understand what is going on with the backend for this at all. > > There is nothing special about either MediaWiki's LESS support, or the > MediaWiki UI modules. MediaWiki doesn't even use custom PHP LESS functions > anymore, and you can still write skins in 100% CSS. > > I don't understand what part of the backend you feel blocks your work on an > alternative skin for MediaWiki UI. mwui has to have some kind of framework for the form elements, or it would be impossible to reliably style anything beyond the buttons (css is just not that well supported for form elements on all browsers). But I've seen other form elements in the prototypes. How was this done? -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
