(no subject)

[nonelvis]

Via /., Google is telling Gmail users to drop IE6.

KILL IT, GOOGLE. KILL IT WITH FIRE.

Comments

[platypus]

IE6 should have been buried years ago. Ugh.

I finally have Firefox 3. It hasn't solved my LJ comment indenting problem. I guess I'll post on the support board, but it strikes me as really weird that nobody else has mentioned it, and there doesn't seem to be much point posting on a holiday weekend. Anyway, someone'll probably just quote some irrelevant point from the FAQ at me.

[miz-hatbox.livejournal.com]

From what I've tasted of IE6, I hold with those who favor fire.

[iainpj.livejournal.com]

Not that Google has even the teensiest amount of self-interest in this issue now, oh no no no! Not that I would necessarily object to IE 6 dying. Unfortunately, until they do something to make Exchange Server more compatible with other browsers -- which will happen someday after the twelfth of never -- or until IE 8 comes out and gets annointed with the approval of our IS department, I'm stuck with the critter.

I will admit that the one major benefit of no longer doing web development is not having to sit there and go, "It works in Firefox! It works in Safari! It even works in Opera! and ... do we have to look at it in IE? Really? ... Well, hell." The latest version of our website only completely works in IE, and that only because it's somehow set such that when you tell IE to change text size -- our designers were unfortunately members of the Teeny Type Brigade -- it basically says, "Yeah, right. I spit on your desire to be able to read this site! Ptui!" In Firefox and Safari, the text size changes, and you wind up with text in one section overlaying text in the one above. Very very Special.

FWIW, I can't find any indication that Google updated the Webkit that they used to develop Chrome to a newer version, and they don't seem to keep a Chrome changelog, so it's probably still a profoundly unsecure browser, as these things go.

[nonelvis]

You win this thread.

[nonelvis]

I'm well aware Google has some self-interest here, but as a web designer, I want IE6 DEAD DEAD DEAD. (BTW, if you don't already know, the problem with your website is that the designers specified type in pixels or points instead of a relative unit, like ems; change it to something relative, and IE6 will happily resize the type.)

You aren't the only person I know who is forced to use IE6 for work, and you have my sympathy.

[nonelvis]

That's very weird. What exactly is it doing, and does clearing your LJ cookies fix the problem?

[platypus]

I think I broke something.

[(Anonymous)]

Huh, that was weird. The login box in the main page wasn't working for me, so I tried logging in while posting a comment, and it worked. I thought I could edit that comment once I was successfully logged back in, but there's no edit button. I guess it's not in your journal style. Uh, I have to go reset some things now. :)

[nonelvis]

Man, I don't know *what* you did, but based on your anonymous comment, it must have been very special. Congratulations!

[platypus]

Right, okay, clearing cookies does not help (though it's something I should have tried a week ago). Firefox helpfully blocked all subsequent cookies from livejournal.com when I deleted the existing ones, hence the few minutes of why-can't-I-log-in flailing.

Anyway: when comment pages are rendered in the site scheme (any site scheme), threaded comments don't indent. Everything's against the left margin, which makes the threads really hard to follow. (But it's not the same as view=flat; the comments are in threaded order. In fact, when I load the page they show indented properly for an instant and then jump over to the margin.) I don't think it's related to the 'expand' button -- unexpanded comments are behaving the same way. It started a couple of weeks ago; I thought it was just Dystopia finally breaking, but every site scheme is doing it for me. Only on the Mac, and only in Firefox, but it's the same in 2 and 3. I can't be the only Livejournaler out there using this setup; why hasn't anyone else complained?

I can fix it by forcing comment pages into my own journal's style, but I don't like that, and it's a pain in the ass appending ?style=mine to the entire anonymeme.

...damn, Safari works. I don't really want to change browsers.

[iko.livejournal.com]

Ohpleaseohpleaseohpleaseohplease...

[nonelvis]

I HATE that cookie-clearing behavior of Firefox's. It did it in version 2 as well, and it's incredibly annoying.

The only other possibility I can think of for why you're seeing this display in FF is that it's loading some other file with CSS positioning info that conflicts with LJ's. But in order for that to happen, you'd have had to specify a different default CSS file to override everything, and I really doubt you did that.

Even so, it might be worth nuking your FF preferences. Back up your bookmarks first, just in case; they aren't stored with this file, but better to be safe than sorry. Then delete ~/Library/Preferences/com.mozilla.firefox.plist. If you have other com.mozilla files lying around, you may want to kill them too (unless you have a Thunderbird plist file, because that's got your mail preferences).

[nonelvis]

::prays with you::

[kalleah.livejournal.com]

AMEN. The latest version of the CMS that we produce is officially unsupported in IE6 (at least the admin stuff) and we all did the dance of "DING DONG THE WITCH IS DEAD" when it released. Except now we have people who won't upgrade because they need IE6 for other products.

Anyway ... the sooner we move away from IE6 the better. I use Firefox for most things on my home PC except Gmail (which is in a Chrome application shortcut) and occasionally Opera when I feel like being different. IE7 only gets used for Netflix streaming and it aggravates me every time I have to switch over.

[nonelvis]

I hate IE7 less than I hate IE6, but I don't think it's possible to hate anything as much as I hate IE6.

I do have one client stuck on IE6 because their IT department claims it's the only browser supported by a particular software package. It turns out that the client is several versions behind on this software package, and IT just can't be arsed to upgrade and save everyone the pain of using IE6. Your customers may be blessed with equally wonderful IT folks.