5 ms·

I think Windows wanted to use a UI language that had a solution to vertically centering an element, and other kinds of more advanced constraint-base layouts. I

• 0xCMP 9y ago
  And they did fix that for the JS applications (WinJS and the like) by using and implementing their own idea, the "grid", which no one else supports to this day, but in a lot of ways is based on the ideas of UI design from XAML/WPF.
• c-smile 9y ago
  That's true. Desktop UI has a set of requirements that is still not achievable in modern browsers (and inherently in Electron). Conceptually there are still no ways at the moment to reproduce full set of canonic layout managers from AWT: https://docs.oracle.com/javase/tutorial/uiswing/layout/visual.html https://docs.oracle.com/javase/tutorial/uiswing/layout/visua... Partial attempts to introduce flexibility in CSS were made only recently - flexbox and grid specifications. But even those attempts look quite random and far from being well thought. For example concept of flex (portion of free space) in flexbox is defined by property flex, but in CSS Grid module the same concept is defined by 'fr' free space units. Yet the same entity in HTML was initially known as * (asterisk) units (<frame> and <table> metrics). (All these are expressed by * units in Sciter in their initial meaning). I suspect that such no-one-is-responsible-for-overall-architecture in CSS was one of major motivations in XAML/WPF appearance.