4 ms·
With HTML 5, visual consistency could be achieved more easily: instead of manipulating the DOM, we can write our own presentation code using the canvas element
by ryanmarsh 9y ago
With HTML 5, visual consistency could be achieved more easily: instead of manipulating the DOM, we can write our own presentation code using the canvas element
First we'll start by breaking the browser and everything that integrates with it.
FTFY
- jcranmer 9y agoI mean, it's not like the DOM does anything useful, like let blind people navigate a website.
- groby_b 9y agoThen we'll promptly forget about a11y. There are many shortcomings to HTML, yes. "Just replace it" is not the right answer. It has never been, for the same reasons that you don't "just rewrite" an old code base. There's more value than the naked eye can see. (Oddly, the web has just the example for that - Netscape 6.0. That was a from-scratch-rewrite, and oh my, was it painful)
- yellowapple 9y agoa11y?
- SirensOfTitan 9y agoAccessibility
- yellowapple 9y agoGot it. Kinda wish we'd stop with this whole "replace the middle of the word with a number" trend, but oh well.
- WaltPurvis 9y agoI agree, but u11y n7ms are here to stay.
- groby_b 9y agoI think that ship has sailed long ago. It dates back at least to the late 80s, when IBM(?) or X11(?) manuals referred to l10n and i18n tools. a11y seems to be slightly later. My memory whispers something about mid-90s. So, maybe not quite as much a "trend" as you assume :)
- yellowapple 9y agoI mean, back in the 80's we had limited RAM and maximum filename lengths and stuff, so maybe there was a practical benefit. By "trend", I more mean the trend of continuing to use these sorts of weird numeric contractions of words instead of just saying "localization" or "internationalization" or "accessibility" now that we have computers that can handle big words without breaking a sweat. I m2n, w2t is t2s, t1e o3n d2s of t2t m5es?
- groby_b 9y agoThere was a much bigger benefit. Try writing those words on a whiteboard, repeatedly, and see what that gets you :) You can argue till you're blue in the face, it's an established shorthand by now. And shorthand has a point - I don't see you writing "random access memory" instead of RAM either.
- yellowapple 9y agoOnce upon a time, RAM was called "core". We should go back to that. I digress... I'll concede it's easier to write on a whiteboard, but for other situations, it seems rather silly (and very different from the concept of an acronym or initialism).
- deleted 9y ago[deleted]
- imhoguy 9y agoAccessibility. Simply by using canvas is like throwing away all human-machine interface support stuff which your OS/browser provide and reminds me times of arty Flash pages with awkward navigation.
- yellowapple 9y agoAnd then we'll reimplement it. Poorly.
- marcosdumay 9y agoHum... Nope, QML has a better DOM (for applications, not text) from the start.
- eropple 9y agoA DOM that doesn't work with a screen reader is definitionally not a better one.
- jcelerier 9y agoThankfully, it does: http://doc.qt.io/qt-5/qml-qtquick-accessible.html http://doc.qt.io/qt-5/qml-qtquick-accessible.html
- eropple 9y ago> instead of manipulating the DOM, we can write our own presentation code using the canvas element That strongly suggests that any Qt accessibility stuff will be thrown out the window.
- marcosdumay 9y agoYes, it throws the HTML DOM out of the window. But if it's built as a native standard, nobody will have to reinvent a DOM, because QML has one, and it's better than HTML's one for applications.
- martin_ky 9y agoI (author) meant that as an example of how you could achieve portability and consistency with HTML5. The canvas approach is NOT what QML does, however. Not unlike HTML DOM, QML builds a tree of objects from the declarative representation (.qml source code) with discoverable properties. It would be straightforward for accessibility tools to traverse this tree and extract information from it. As user jcelerier already mentioned, QML has accesssibility features built-in. It provides a tool to annotate any part of the UI with accessibility metadata. HTML has nowhere near such a consistent approach to accessibility.