Re: [Design] mwui.wmflabs.org reactivated, showing upcoming MW UI styles ($wgUseMediaWikiUIEverywhere = true; )

Ok, I've been thinking about this for a bit. my suggestion is this… We create 3 more controls - Dropdown <https://trello.com/c/bdpbPSZT/4-drawer-menu> (can Juliusz's work on compact person bar be componentized?) - Search Field <https://trello.com/c/MC8ovuyw/2-advanced-input-fields> - Radio Button <https://trello.com/c/df2N2KJx/8-radio-buttons> Finalize 2 controls - Check box (disabled state, disabled checked) - Vform (vertical padding) Then let's make a Beta feature to allow people to test and see medaiwiki.ui in context in vector(at least) and report problems. I'd love to be able to provide a fixed element on screen that allows someone to quickly and easily report problems with a control on a particular page (isn't using mediawiki.ui style, isn't using right type (progressive, constructive, destructive) and right style normal, quiet, etc. and any issues around order or logic, e.g. on WTE Save should be the rightmost according to mediawiki.ui guidelines and there are too many Primary style buttons. *Jon*, perhaps you could brainstorm a fixed header element that allows someone to report an issue on their current page that generates bug reports or emails or something along those lines? Is there any way we could accelerate fixes reported by users more than our normal time span of 2-3 weeks? cc'ing *Greg* for his thoughts here about a way to do this without breaking things. This won't be our first Beta feature that is more for learning and testing with no plans to graduate but we should be clear that that's what its for in the description on the beta page, so people can give helpful and constructive feedback knowing that it will be an iterative process.