Why there are 2 pages #2 on each screenshot?
A subtle layout bug in Google Search: When CJK text-wrapping meets float
21–26 of 26 posts
Re: A subtle layout bug in Google Search: When CJK text-wrapping meets float
#22Fascinating article! Weird side note but lovely note callout. I’ve been trying to get something similar on my site but haven't got it to work right. Is the code for your site open source? I check your GitHub and couldn’t find it.
Re: A subtle layout bug in Google Search: When CJK text-wrapping meets float
#23Earlier quoted context omitted.
I would definitely read an in-depth exploration of Google's design failures from someone informed & opinionated on the topic. I found this looking for such a thing: https://ux.stackexchange.com/questions/81965/what-are-the-di...
I've read a bunch of stuff about their design and why it's so bad, including this one. Bottom line is you cannot scientifically manage your way to design. That is why in the future we are going to see designers with aesthetic sense become more and more useful as AI sort of like starts doing everything.
Re: A subtle layout bug in Google Search: When CJK text-wrapping meets float
#24While following the development of the Ladybird browser[0] I found out many of the Web Platform Tests[1] are related to CJK rendering which I found surprising, but seeing this it makes a lot more sense. [0] https://ladybird.org/ [1] https://wpt.fyi/results/?label=experimental&label=master&ali...
Just wait until you have to test vertical traditional Mongolian sites: http://khumuunbichig.montsame.mn/index.php?home
Re: A subtle layout bug in Google Search: When CJK text-wrapping meets float
#25Re: A subtle layout bug in Google Search: When CJK text-wrapping meets float
#26No, not for Korean. We do have spacing rules like European languages. And we don't like a situation when an arbitrary line break is added in the middle of the word.