6,026 karma · joined October 27, 2019
Good, though doesn't seem to be include the ability to control icons, name and accelerator keys, so still a long way to reach the user ergonomic heaven...
> U+2800 is clearly used as a symbol, to indicate the presence of a space when describing a Braille sequence corresponding to a symbol or punctuation, similar to the use of ␣
Why is that? Have you perhaps forgotten to add "␣" equivalent for Braille? So maybe do that instead so people can us a mark to mark something?
> Especially in cases where it is used in a trailing position, as in the [UNE13] example, it is clear that it would be inappropriate for this symbol to disappear
Nothing disappears in the cited example, the line is very short , how is it possible to reject a fix when you can't even find an example of that fix breaking someone?
> last changed in
and this approach is why we can't have nice things and generations of computer users continue to suffer due to some dumb oversight decades ago. And it's not like we get a payoff of great stability, not, that standard is uber complicated and changes all the time
Go on - define a bar here.
> just that it needs to exceed a threshold
Same. Be specific.
This prompted me to finally dig a bit and find the official reference why they didn't fix the bug despite a plea from some Braille council
https://www.unicode.org/L2/L2025/25183-utc184-properties-rec...
> For example, U+200B ZERO WIDTH SPACE was originally classified as a space character (General_Category=Zs), but it was reclassified as a Format character (General_Category=Cf) to clearly distinguish it from space characters in its function as a format control for line breaking.
The key thing you forgot, which makes this approach non-sensible, is the omniscience, without which you have no clue whether your posture towards a new bug-finding tool is good or not, since you don't know whether it will mostly find those bugs that are not worth fixing and the time wasted on fixing them is detrimental.
Similarly, how is ignorance better than informed decision when ignorance also includes missing critical security bugs?
There are two points in a connection, and one way to sever it is to follow author's advice to "ignore them". Or you could try to learn and maybe even engage.
(also, the "non-coward" way would be to actually link to the comment so that we could try to understand how toxic / irrelevant expert peons are)
For example, non-regulatory attempts at blocking of competitors, which Google does engage in due to their dominant position in mobile (of course, that's also just another better product)
But in general sure, it's not like we have good databases that count and classify bugs and track their numbers and severity and determine causes so we can compare the dynamic
It's a tragedy decades of UI research/design can't get any of the fundamental design elements right