This is why I advised people to stop using mw-ui-input/mw-ui-button on elements like this. It isn't consistent and can actually be quite inaccessible on some browser/OS combinations. --Shahyar On Mon, Aug 18, 2014 at 12:56 PM, Prateek Saxena <psaxena(a)wikimedia.org> wrote:

So... I still lack an answer to my original question. I understand styling select elements involves care, but I'm asking whether they /should/ be styled like mw-ui-inputs or in a completely different way that needs to be implemented. On Mon, Aug 18, 2014 at 10:17 AM, Trevor Parscal <tparscal(a)wikimedia.org> wrote: -- Jon Robson * http://jonrobson.me.uk * https://www.facebook.com/jonrobson * @rakugojon

Currently our buttons look like this <http://tools.wmflabs.org/styleguide/desktop/section-2.html> [image: Inline image 1] And on compact personal bar, the select looks like this <https://www.dropbox.com/s/e7o7ywyhkdggx0h/Screenshot%202014-08-25%2011.58.39.png?dl=0> [image: Inline image 2] and if you look above your gmail search bar input combo box, it looks like this <https://www.dropbox.com/s/gt9twpqrixhninu/Screenshot%202014-08-25%2012.19.39.png?dl=0>. Very similar to ours. [image: Inline image 4] I don't believe we've had complications with users with these styles so far. To set the right expectations for it to be an input field or a select button/menu, it's more than just how the bounding box looks like or limited to that. A drop down caret is important to show that there is some kind of menu happening. A high contrast text within the bounding box is also important to show that this is not an input field. A light italicized placeholder within a bounding box shows that "this is where you should be typing in your response." Even the label is important. I don't think the gmail's search bar is the best execution for a input combo box, but I guess it worked. I would've included more affordance to show that it's an input field, but at the same time, the length of the box and the search button next to it kinda gave it away. So in conclusion, in the effort of being as simple as possible—elements being used for a reason and nothing more with a goal of being consistent as well—I have a strong feeling that this set is going to work! We want to be able to explain what every single element* does effectively without more elements*. [image: Inline image 6] *elements being text, icons, color, line, border, etc. mm On Mon, Aug 25, 2014 at 11:26 AM, Trevor Parscal &lt;tparscal(a)wikimedia.org&gt; wrote:

For more clarity, I labelled each control and am showing how each hover state looks like. [image: Inline image 1] mm On Mon, Aug 25, 2014 at 12:49 PM, Isarra Yos &lt;zhorishna(a)gmail.com&gt; wrote:

Matthew Flaschen wrote: Yeah same here. And why is it grey background? I used to have white background of select boxes everywhere. Matthew Flaschen wrote: Thought this /is/ oojs-ui. What is the thing linked above, then? svetlana

​Isarra, we're designing a single look and feel for controls, community developers are welcome to extend that set to other skins, ​since the skin of these controls will extensively use LESS (right developers?) this should be a trivial task, and while we're happy to give feedback on these community changes for other skins, we do not have the time or resources to maintain skin specific variations. *Jared Zimmerman * \\ Director of User Experience \\ Wikimedia Foundation M +1 415 609 4043 \\ @jaredzimmerman <http://loo.ms/g0> On Tue, Aug 26, 2014 at 10:31 PM, Isarra Yos &lt;zhorishna(a)gmail.com&gt; wrote: