RSS feeds in the directory: 374
Added today: 0
Added yesterday: 0
On 25 September the working group of CSS in W3C released the first public draft module of the scrollbar (Scrollbars CSS) level 1. By design, it needs to provide a standard means in order to be able to seamlessly fit, scrollbar in different themes (dark, contrasty, compact, etc.), not breaking with the native functionality of the platform. But the choice of funds offered by the draft, many may surprise you.
as the editors of this module are shown Tantek çelik of Mozilla (it is also known as the Creator of microformats) and Rossen of Atanassov from Microsoft. But judging by the log in the issue tracker, mostly it was the work of the staff of Mozilla — Celik and his colleague Sidor Quan.
to Surprise the new module starts from the first paragraph: "CSS Scrollbars standartisied the ability to paint, scrollbar introduced in 2000 in IE 5.5 for Windows." And really, there is taken not pseudo-elements ::-webkit-scrollbar -* to which many have grown accustomed, namely those ancient Esnie properties like scrollbar-face-color, scrollbar-3dlight-color, from which long since refused to IE. At first editorial draft got all those Esnie properties, but then their set was reduced to two — color strips scrollbar and the color of his slider. And then combined them into one property scrollbar-color, taking two color values separated by a space. Another property — scrollbar-width — controls the thickness of the scrollbar. These properties are already implemented in Firefox for the flag layout.css.scrollbar-colors.enabled and layout.css.scrollbar-width.enabled in about:config, respectively (the above screenshot example of their actions).
many web developers solution Celik and his colleagues were puzzling, and module editors even had to add a subsection explaining the "why doesn't pseudo-elements". In short, the arguments are as follows: 1) the WebKit developers themselves have even admitted that open for all the implementation details of a scrollbar in one platform was a mistake, 2) the OS is constantly evolving, and one set of pseudo-elements may fail to capture the evolution of the scrollbar in them, and 3) in different platforms, the structure of the scrollbar is different, and to find a universal set of pseudo-elements hard for them. But many, including me, these arguments are still not enough to convince. In my opinion, the second argument in the same measure applies against a fixed set of properties. In addition, the properties do not allow to flexibly control the behavior of the parts of the scrollbar when the mouse cursor is (in the first implementations in Gecko it did not was being processed now at the mercy of the browser). In my opinion, this question is too early to consider, disagree with the decision quite a lot, and it makes sense to open the corresponding ISU again, adding counter-arguments. What do you think?
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
Amazing and unknown inline-block 24.07.2018 at 12:43
Chemistry CSS grids 15.07.2018 at 12:48