RSS feeds in the directory: 374
Added today: 0
Added yesterday: 0
The design of the form elements is probably the main source of pain in a modern layout. Each input field, each button — a "thing in itself", and in each browser is implemented slightly differently. And manage their styles too often in each browser differently. And some tasks (for example, to display the button as a normal an element with display: inline, wrap to a new line if necessary) and does not solved (apparently this effect gives the display: contents, but in the present implementations, this breaks accessibility so that is not a solution). A lot of hope for deliverance from this pain was attributed to the appearance property, but the fate of this property was complicated and confusing. Now there's only old browsers implement it with a prefix, is also everywhere, and none of them solves the problem completely.
so, while all browsers with anger did not copy "in a forehead" -webkit-appearance, and not added to the list of "non-standard standards" de facto, after a long discussion in ICU on Github longtime activist web standardization Simon Peters decided to take matters into their own hands and to outline the "correct" draft specification of this property — taking into account the wishes of the designers, and browser reality. And finally to standardize themselves, and browser styles for form elements, and how they are reset.
the Work will be huge, but the pace is taken good. Within days the blank document on Google Docs has grown to an impressive 19 pages. Given the experience of Simon's work on the WHATWG spec, where as a lot of times had to "lead to a common denominator" raznoobraziya zoos implementations, it is hoped that this time everything will work out!
Why don't we add in a HTML element ? 11.10.2018 at 12:56
"The dispute over empty space" and the change in selectors level 4 04.10.2018 at 10:40
The first (and strange) the public draft of CSS module scrollbar 28.09.2018 at 13:39
Why semantic HTML is important, and how TypeScript helps to understand it 24.09.2018 at 10:15
Nobody knows the CSS: specificity — not cascade 13.09.2018 at 13:02
New candidates the W3C: CSS Display and CSS Cascading 3 and 4 28.08.2018 at 14:03
Solved with CSS! Logical pastiche based on the number of elements 25.08.2018 at 09:44
The first public draft of module quantities and units CSS level 4 15.08.2018 at 15:51
Freshly updated CSS drafts: overflow level 3 line layout level 3 grid level 2 05.08.2018 at 18:00