- From: Daniel Tonon via GitHub <sysbot+gh@w3.org>
- Date: Sat, 10 Feb 2018 22:53:56 +0000
- To: public-css-archive@w3.org
> They're potentially not even correct cross-platform - it's allowed for things to render differently between UAs, and in particular to switch between text-like and button-like on mobile vs desktop The color input is a perfect example of this. It appears often in desktop as a text field but appears more like a button on mobiles. Instead of specing it to say "these specific input types are `:text` and these specific types are `:button`" I think it should be speced to say "Hey browser, if you think the input looks like a textbox then include it in `input:text` if it looks more like a button then include it in `input:button`". By letting the browser decide what is a textbox and what is a button it makes the spec far less brittle. It also could allow for more control over form elements. I've often seen `input[type=file]` display as a text field with a button next to it. By letting the browser decide what is `:text` and what is `:button` it could mean that the textbox part of the input could be styled with `input:text` and the button part of the input styled with `input:button`. That would be more like styling pseudo elements though so maybe `input::text` instead of `input:text` (double colon for psudo elements) -- GitHub Notification of comment by Dan503 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2296#issuecomment-364702484 using your GitHub account
Received on Saturday, 10 February 2018 22:53:58 UTC