I keep ranting we need a state-ful GUI markup standard so that we don't have to keep reinventing GUI idioms in HTML/CSS/JS, which are NOT MEANT for that job. Re

I keep ranting we need a state-ful GUI markup standard so that we don't have to keep reinventing GUI idioms in HTML/CSS/JS, which are NOT MEANT for that job. React et. al. have long learning curves because of screwy edge-cases, glitches, and JS's lack of type-saftey. The GUI markup browser-and/or-pluggin could be built on top of the Tk or Qt GUI kits to avoid starting from scratch. Put a nice XML wrapper over those C/C++ libraries and you have a GUI browser. Missing or poorly-done GUI idioms in HTML/DOM: * Stateful-ness tied to session * Predictable & consistent text positioning * Split-panels/frames (HTML5 butchered them) * Combo-boxes * Nested drop-down menus * Context menus (right-click) * MDI/dialog ability tied to session * Tabbed panels * Tool-bars * Sliders and turn-knobs * Editable data-grid * Expandable trees * "Normal" multi-select * Status bar (newer browsers screwed them up) * Fuller keyboard shortcuts. * Graphic/art elements & data inputs at same time * Consistent & biz-friendly number & date inputs Fuller descriptions: https://www.reddit.com/r/programming/comments/otixwo/comment/h6zi86w/ https://www.reddit.com/r/programming/comments/otixwo/comment...