What the deuce? Why can't I type in certain areas using XCode? [more inside]
posted by designbot on Jul 23, 2008 - 4 answers

I'm disappointed with the service I'm getting from an Apple authorised repair centre. Where do I go from here? [more inside]
posted by snarfois on Dec 4, 2007 - 11 answers

WoWFilter: Help me win a friendly bet involving World of Warcraft macintosh bugs, screen layout, and character positioning. Yep, lots [more inside]
posted by cowbellemoo on Nov 29, 2006 - 4 answers

IE5 Mac bug (I think): A site I am working on looks fine on all platforms except IE 5.2 Mac. Basically, it adds space around [p] elements and inside [td] elements which shouldn't be there, and misinterprets selectors in baffling ways.
Is there a well known way to fix this kind of behavior other than saying 'to hell with it'?
posted by signal on Dec 7, 2004 - 9 answers

Help, I'm stuck in IE/Mac hell! (It's the only browser we support for Mac at the moment, so it has to work there.) I have a dropdown list with various values: Page 1, Page 2, Page 3, etc. One of these values is set by the JSP as the current selected value: Page 3 . Clicking on the value in the dropdown you want (Page 5, whatever) will bring you to that new page. The code is valid and works perfectly fine in IE/Win, Safari, Mozilla, etc. But on IE/Mac, when the new page loads, the value that's *visible* on screen in the dropdown box is not the currently-selected one, but rather whatever value was the first value in the dropdown list! So you could be on Page 1, go to Page 5, but Page 1 (the first option in the list of options) is what displays in the dropdown. To make matters funkier, when you then click to open that dropdown, it "jumps" to show you that yes, you're really on Page 5, that Page 5 is indeed the selected/highlighted value. So it's a display bug of some sort...?

I've seen plenty of bug reports and workarounds online for Mac/IE, but nearly all of them involve CSS, not core HTML pieces like options/selects. We do use CSS on the site, but it's minimal, and we generally use nested tables, inside which this naughty dropdown resides. Ideas to get around this--maybe javascript to force the correct value to display? Anyone else had this sort of issue? Help!
posted by Asparagirl on May 27, 2004 - 2 answers