• zelon88 2 hours ago

    Not surprising.

    The homepage of Google has n-e-v-e-r had an error free console, which I find funny considering it's literally a white page with a logo and a lonely text field, and considering that Google expends so much effort trying to sling their design methodology onto everyone. "Do as I say, not as I do."

    • simlevesque 25 minutes ago

      > The homepage of Google has n-e-v-e-r had an error free console

      I just checked, mine is error free.

      https://google.com

      Are you sure it's not your ad-blocker or another browser extension that causes this for you ?

      • ilrwbwrkhv 26 minutes ago

        Well I hope nobody follows Google's design philosophy seriously. They are among the worst in the business.

        I've said this for a long time, but the only reason Google search was successful is because they were lucky enough to just have a text area for the search box. If they had tried to do anything else, they would have drowned miserably because their design choices and decisions are so bad.

      • JeremyBarbosa 2 hours ago

        While 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...

        • mananaysiempre 42 minutes ago

          I thought those were on CJK encodings like GB 18030 and Shift-JIS? (Absolutely massive and one of the few places you’ll still encounter the insane stateful four-charset switching monster that is ISO 2022, so deserving of a lot of testing.)

        • tapirl an hour ago

          Another problem for years in Chrome is, if a line is wrapped between two Chinese words, Chrome will insert a space between them in rendering. (Firefox doesn't)

          • silvestrov 2 hours ago

            In short: don't use "float: left/right" for anything besides real floating images.

            In this case a "display: flex" on the <a> element would be a much better solution.

            • londons_explore 2 hours ago

              I wonder how long ago this CSS was written...

              That particular UI element of google search has been around decades, so might predate css flex...

              • ipaddr 2 hours ago

                2009 but css flex didn't become popular until 2014+.

                • mananaysiempre an hour ago

                  In 2009, one still needed to give IE6 serious thought (even if, depending on the use case, the conclusion could already be “nope”). At the time, I had someone telling me that we shouldn’t waste our time on supporting mobile. And flexbox was more a curiosity you studied with a hope of using someday than a serious option.

                  And clearing your floats was part of the absolute basics. Of course, we still forgot to now and then.

            • eimrine 33 minutes ago

              Why there are 2 pages #2 on each screenshot?

              • clacker-o-matic 2 hours ago

                Fascinating 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.

                • DimuP 3 hours ago

                  Now i have to learn html again