Slashdot Mirror
Apple Details CSS Bugs in Internet Explorer for Mac
Isbiten writes "An article at Apple Developer Connection discusses all the CSS bugs in Microsoft Internet Explorer, and compares IE to other browsers, including Mozilla." Wow, they sure do.
← Back to Stories (view on slashdot.org)
Now, correct me if I am wrong, cause, hey, I probably am, but does this not seem like just one more subtle insult from Apple to Microsoft? Well-deserved, I might add, but why all these recent jabs?
The switch ads are the obvious, but I find this, and the fact that MS's recent fake switch ad made it to Apple's Hot News page quite interesting from a company that publically expressed all is well between them and MS.
Besides, When you're trying to convince MS users that they can use Mac versions of programs they are used to, why point out serious flaws in one of the biggies??
Unless, of course... you have something better you're planning to push.... (Which I'm not saying must be the oft-rumored iBrowse. Could just be Mozilla)
John Kenneth Fisher
Table of malContents
I wouldn't be surprised if it were written by the same person. Apple tends to listen to developers and will post technical documentation that users provide.
Out of curiosity, what exactly do you class as properly supporting drag and drop? I've just played around with it in Chimera, and it seems to work as I would expect. Only noticeable difference between it and Internet Explorer is that Chimera displays a grey rectangle representing the dragged text where Internet Explorer displays a grey border around highly transparent text. Neither of these behaviours is consistent with drag and drop from other Mac OS X applications, but I fail to see how Internet Explorers is more correct.
I have the same problem with IE on OSX. Very annoying, having to keep clicking around text on a page to try and make it visible and have other parts of the text blink out of existence. I haven't seen this addressed anywhere, either. Anyone have any info on this?
"They" (meaning many of those responsible for the OS X experience) feel very strongly about it and are doing something about it. One day Software Update will do something about it for you.
The last five years have restored Apple to relevance. They stand poised at the greatest crossroads in their long, storied history.
They face difficult, but familiar challenges: are they sufficiently WinTel compatible? Can they remain competitive on the performance front? Will developers support their software initiatives? Can they match WinTel development tools for productivity and power? Must they continue to rely on Microsoft Office to validate their platform? How can they meet all these challenges and remain innovative?
Say goodbye to Office and Internet Explorer. Soon they'll be as supported as the Visual Studio 4.1 Macintosh compiler.
IE for Mac has some major problems in terms of positioning. In one example I had, what was supposed to be a footer at the bottom of each page, was now somewhere above the top of the page, completely invisible.
I can live without support for targeting child elements, but I can't live with bugs that will render pages useless to users.
One thing no browser seems to do well - and MSIE on the Mac is abysmal at this - is ignoring threads which have no purpose anymore, as the user has chosen to hook up with a new link.
Scenario: You start to load apple.slashdot, and there are a lot of embedded URLs. About 10% through the load you see a link you want to jump to immediately. So you click it. If you do this on IE for the Mac, you can wait a long time, because the brainiacs who write IE for the Mac let this poor thread compete with all the others already in Q. When it finally gets its chance to run, you can see some progress, but until then you will load GIF after GIF etc on a page you no longer want to see.
It is painfully obvious that all these GETs should be ignored, the threads they run in should be orphaned, but it is as per usual obvious the Microsofties just don't get it.