You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just a little thing, but I notice that depending on the font, the ? question marks can look a little odd:
Upon inspection, I see that these aren't normal question marks ? but actually ﹖. I see that this (U+FE56) is the "small question mark", but I'd suggest that the size is probably better handled with CSS than the use of unusual unicode characters.
The text was updated successfully, but these errors were encountered:
I used that funky question mark because it looks more readable when set to a tiny font size. A regular question mark looks odd when downsized. We could consider a CSV question mark icon so that it is independent of the font used. Thoughts?
I used that funky question mark because it looks more readable when set to a tiny font size. A regular question mark looks odd when downsized.
This sounds like a rather font-dependent thing then. I'd expect a small sans-serif question mark should be fine at small sizes, particularly if the weight was increased. I've been doing some UI tweaks to my deployment, one of which is using a normal question mark (?) and even without increasing the font weight it looks fine on my end:
A SVG question mark icon (which I presume is what you meant by "CSV"?) would also work here, but I feel might be overkill? It would be good to see how this is with a fer different fonts.
It occurs to me we could probably also justify a bigger/more obvious question mark if they were only shown on hover.
Hello!
Just a little thing, but I notice that depending on the font, the
?
question marks can look a little odd:Upon inspection, I see that these aren't normal question marks
?
but actually﹖
. I see that this (U+FE56
) is the "small question mark", but I'd suggest that the size is probably better handled with CSS than the use of unusual unicode characters.The text was updated successfully, but these errors were encountered: