This is good advice, but the problem is that there is so much good advice about webdev (and everything) that one tends to form a FIFO queue in one's brain such that the advice is inevitably lost.
Add dir=“auto” to your inputs and textareas
81–90 of 114 posts
Re: Add dir=“auto” to your inputs and textareas
#82dir is a global attribute that can be set on any HTML element: https://developer.mozilla.org/en-US/docs/Web/HTML/Global_att... What I don’t understand is why dir="auto" isn’t set as the default value, allowing browsers to choose text direction based on the lang attribute or the text content.
It affects float direction. Imagine the browser detecting Arabic text and suddenly all your float lefts are floating right. Switching it from one side to the other will completely break a lot of layouts, particularly older ones.
Good thing that there is no reason anymore to use float to hack page styles, instead of floating objects within your text. So that switching the direction is the correct thing to do with reasonably placed float out there.
Re: Add dir=“auto” to your inputs and textareas
#83Earlier quoted context omitted.
I am not "gatekeeping", I'm telling you that in spaces you don't know there's hidden complexity, and you shouldn't rely on the Internet. No amount of "awareness" is taking that away. Also, please tell me where I "belittled" the author.
Uh. It was probably the uh. I don't fault you for thinking it might be something else.
I honestly had no idea what it was, so thanks for the explanation. Wish I'd gotten your reply sooner, because I'd just have taken it it out.
Re: Add dir=“auto” to your inputs and textareas
#84Earlier quoted context omitted.
Instead of gatekeeping "the space" with insider abbreviations and belittling the author, you could appreciate that they raised awareness of the issue.
At what point is someone 'allowed' to criticize an author's approach and point out another that would have made their struggle shorter? Accusations of gatekeeping should be accompanied with evidence of malice if they are to be taken seriously. Correcting (or, more like augmenting) someone speaking authoritatively on something is not gatekeeping. Also, gatekeeping has a social value, when used at the right time in the…
Here's another way groby_b could have said the same thing:
"I spend a lot of time designing UI for international users. In these circles, the issue you're talking about is referred to as 'BiDi' text input. If you would like to know more, ping me! Sometimes Googling isn't fruitful if you don't already know the lingo."
Maybe this sounds better to you, too. If not, maybe I'm wrong. It happens a lot. :-)
Re: Add dir=“auto” to your inputs and textareas
#85> The first results page of Google never lies...
I have something to tell you that will help you solve your problem, but you should sit down first, because it's probably going to make you sad...
Re: Add dir=“auto” to your inputs and textareas
#86Earlier quoted context omitted.
Instead of gatekeeping "the space" with insider abbreviations and belittling the author, you could appreciate that they raised awareness of the issue.
I am not "gatekeeping", I'm telling you that in spaces you don't know there's hidden complexity, and you shouldn't rely on the Internet. No amount of "awareness" is taking that away. Also, please tell me where I "belittled" the author.
I think it was the "uh." :-) If I read it without it, it's not so bad. And I know we all dash off comments quickly sometimes. Apologies if I overreacted.
Re: Add dir=“auto” to your inputs and textareas
#87> The first results page of Google never lies... I have something to tell you that will help you solve your problem, but you should sit down first, because it's probably going to make you sad...
> I have something to tell you that will help you solve your problem, but you should sit down first, because it's probably going to make you sad...
I think you are responding to this sentence read literally:
> The first results page of Google never lies, so I thought this was just inherently a problem that required direct intervention, and so was never quite able to prioritize it (so much for my moral high ground).
but I'm almost 100% confident that it was meant with the sarcasm that it deserves, as indicated by the later sentence:
> Google has been lying to us about RTL support in inputs.
Re: Add dir=“auto” to your inputs and textareas
#88> The first results page of Google never lies... I have something to tell you that will help you solve your problem, but you should sit down first, because it's probably going to make you sad...
> I have something to tell you that will help you solve your problem, but you should sit down first, because it's probably going to make you sad... I think you are responding to this sentence read literally: > The first results page of Google never lies, so I thought this was just inherently a problem that required direct intervention, and so was never quite able to prioritize it (so much for my moral high ground). b…
> I think you are responding to this sentence read literally
I think you are responding to this sentence read literally:
> I have something to tell you that will help you solve your problem, but you should sit down first, because it's probably going to make you sad...
but I'm almost 100% confident that it was meant with the sarcasm it deserves.
Re: Add dir=“auto” to your inputs and textareas
#89Sadly, both the website and the linked codepen render the source quite poorly. The period is in the wrong place! The rendered HTML is fine. I assume this is just the Unicode bidirectional algorithm failing, as it is wont to do. I imagine that a special cased algorithm that understood that HTML tags (the stuff between inclusive) should render as atomic things, internally LTR, but without imposing their direction on su…
The Unicode bidi algorithm isn't failing here, it's working as designed. The source code snippet has base direction LTR, but has mixed-direction content because of the Hebrew text. Punctuation marks have weak directionality, so the period shows up at the end of the RTL run. Since the base direction is LTR, the 'end' of the RTL run means the right side. If you want to force mixed-direction content to render correctly,…
You are correct. I explain this in depth here:
Re: Add dir=“auto” to your inputs and textareas
#90Earlier quoted context omitted.
This should be the operating systems problem to solve not developers of every website ever. Same with spellchecking, emojis, copy/paste etc. From from your mouth to God's ear. I wish every program would default to system-wide settings. But unfortunately, too many do their own things. Why does Microsoft Office need a separate dictionary from the rest of my computer? Why does Wrike intercept ⇧⌘N? Why doesn't Adobe Phot…
To be fair, it also wouldn't make sense for Office to have different dictionaries between its Mac and PC (and web) versions. So one or the other has got to give. Users want OS's to be consistent across apps, but users also want apps to be consistent across OS's. And so the reality is each feature is going to be decided on a case by case basis and the end result will be somewhere in the middle.
it also wouldn't make sense for Office to have different dictionaries between its Mac and PC (and web) versions.
Why?
99.9% of people using Microsoft Office are using it on one computer. I'd wager the majority of those people aren't using only Microsoft Office and nothing else.
If Office used the system dictionary, then people's added words would exist in every application they use, and not just every application except Office.