Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The "problem" with native controls is that they might visually clash with the design of your website. That's why everybody implements their own controls or uses libraries like jQuery. And sadly, that's probably why we don't have good default controls.


> The "problem" with native controls is that they might visually clash with the design of your website.

CSS can fix that once good native controls are implemented.


That requires the ability to style things like the dropdown of the combobox (e.g. to add rounded corners, change the background/border colour), and the rows for each items (e.g. adding padding, and divider border styling). At the moment, that is difficult because they are not part of the HTML box model. And what about styling controls like date input or colour pickers?

Another issue is styling checkboxes to use custom images for the different states (including hover and pressed styling).

The CSS UI spec (https://www.w3.org/TR/css-ui-4) doesn't detail any of that, and the WHATWG HTML spec only defines the values of input fields (e.g. https://html.spec.whatwg.org/#the-input-element), not what parts of things like a date control are available and how to style them.


People use JS to implement basic things like scrolling a page, usually resulting in a experience that’s uniformly worse than the native one would be


I have trouble seeing this as a problem, especially with electron and other local web-tech stacks.

I miss the days when clickable things looked clickable.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: