4 ms·

Ex-Wave, Ex-Plus engineer on why javascript is required to read a blog entry. No, it should not be.

• there 15y ago
  and then readability to fix the ridiculously thin font http://i.imgur.com/9Oy37.png http://i.imgur.com/9Oy37.png
  • w1ntermute 15y ago
    What browser/OS are you using? It looks fine for me (Win 7 + Firefox): http://i.imgur.com/BNjXj.png http://i.imgur.com/BNjXj.png
    • josegonzalez 15y ago
      Chrome on OS X.
      • w1ntermute 15y ago
        Hmm, I don't have an OS X machine to test it on. Chromium on Linux looks like this: http://i.imgur.com/kEiQ2.png http://i.imgur.com/kEiQ2.png I think it's an issue with the font renderer or font specific to your browser/OS combination.
      • deleted 15y ago
        [deleted]
• ctide 15y ago
  You're right, javascript should be required to browse the web, not just a blog entry.
• bobbyi 15y ago
  If it's any consolation, it doesn't work with javascript either. I middle-clicked the "previously described" link and it took away the blog entry that I was in the middle of reading.
  • jerrya 15y ago
    I see this at many sites, including, most frustratingly of all, within Google's various help sites. I don't know enough Javascript to understand why that behavior is so often created. Is it so hard to respect the "classic" "canonical" middle click behavior?
    • dmit 15y ago
      It's a WebKit issue: https://bugs.webkit.org/show_bug.cgi?id=22382 https://bugs.webkit.org/show_bug.cgi?id=22382 http://code.google.com/p/chromium/issues/detail?id=255 http://code.google.com/p/chromium/issues/detail?id=255
      • jerrya 15y ago
        Wow. Seems like such a simple and obvious problem and fix, it's educational to see how long it has taken to not get fixed.
• acqq 15y ago
  And I didn't manage to read it with Javascript and IE8. It seems that it's all because he uses http://sitebricks.org/ http://sitebricks.org/ for his site. It is also unreadable the same way.