13 Comments on “Fluther on Chrome”

• Since Chrome uses WebKit, shouldn’t Fluther look the same there as it does in Safari, Midori and whatnot?

  15 years ago Vincent

• Works great, as far as I can tell.

  15 years ago Eambos

• @Vincent… my guess is that the “more correct” typeface rendering* is something that’s either not part of WebKit, or they elected to leave off. Do you know if that piece is available in the WebKit?

  * = http://www.joelonsoftware.com/items/2007/06/12.html

  15 years ago robmandu

• @Vincent- Technically, yes. But in the browser world, I’m a lot more tentative saying “should” than I used to be.

  @Eambos- Thanks. Glad to hear it.

  15 years ago ben

• it’s a fun browser if you’re using windblows, when i use safari on it, it feels so out of place, yet chrome feels…right in the middle

  15 years ago Iwamoto

• Wish I could download it… Come on, Mac version!

  15 years ago shadling21

• Sorry to see this so late – it never occurred to me Fluther might NOT work on Chrome. I have such faith in you guys! Anyway, it works great!

  (Unlike a certain website some of us may have come from… and yes, websites that won’t run on it identify the site as using a version of Safari it is not compatible with.)

  15 years ago EmpressPIxie

• Has anyone tried compiling it for Linux or Mac yet? I’ve heard nothing but horror stories thus far, with no actual product being usable at the end of it. Maybe I will so I can check fluther using it.

  15 years ago tWrex

• I’m having some difficulties with a footer floating into the middle of the page using CSS as I redevelop my website. I hate the fact that there’s yet ANOTHER browser out there that I have to take into consideration.

  15 years ago WebmasterWilliam

• It’s definitely a clean slick look. But I have waaaay too many awesome plugins for Firefox to just switch to Chrome. Besides, I don’t want my Most visited sites showing porn.
  j/k I am a nice boy.

  15 years ago windex

• Your website’s message for Google Chrome dev builds is inexcusable.

  “Chrome/Chromium dev builds are known to contain a serious bug at this time. Please use the stable builds.”

  So what? This poses NO RISKS to you! This only poses a risk to the one using the browser, not to the website itself.

  Douchebags.

  13 years ago GCUser

• I’m not sure to what degree a bug that happens to only affect the newest and most patched revisions of a browser would warrant such action. What, exactly is the bug?

  13 years ago antimatter15

• We only blocked dev builds for a couple days. Google released a build that in certain scenarios would open endless sockets and basically DDoS a site. It actually brought our site down for a few minutes at one point. I hope you understand why we temporarily blocked Chrome dev builds and regardless they are now allowed back.

  13 years ago Tim Trueman