I absolutely hate IE for mac.
I had a really nice ajax (can we pick a better name for this, please? Someone?) note-taking function, and I go to demo it to the client, and see the horror of IE for Mac, which I totally, utterly forgot about. It's as if, as a defense mechanism, my mind completely eliminated any references to IE for Mac.
So now I'm sorting through an Apple article about
Remote Scripting, and rewriting it to use a hidden IFRAME for data. I was encountering some weird problem, and then I realized why things weren't loading properly using the IFRAME. I was making one remote call, then immediately making another. The second call was using the IFRAME before it was done with the first, so the first call was being lost. Since I currently only have 1 IFRAME on the page to perform these calls with, I'm left with the ugly options of:
- Make a queue for the asynchronous calls, and work through it sequentially.
- Add another IFRAME so I can do things in parallel, and set the two calls to use their own personal IFRAMEs
One unnecessarily serializes the process, the other is just, well, ugly. If I want to put more than one, then I might as well implement something generic that takes a list of IFRAMEs and does something similar to connection pooling. That'd be kinda neat to write, but I shouldn't
have to write that, and thats the sort of thing that, when all its all written, would leave me with equal feelings of pride and self-loathing.
At any rate, it's sure as hell not getting done tonight. It's
beer time.