In addition to memorizing the rules, you'll also memorize the specific IE bugs; see a page in IE all messed up, and be able to go, "Oh, I know what would cause that," and be able to fix it without spending hours tracking down the bug.
Comet in IE6? Can you elaborate a bit? I recently had a need for a comet thingy (but not cross-browser compatibility) - so I made a small solution with x-mixed-replace. I don't even know where would I start with IE6, since even later versions are their own world.
Long polling is possible in every browser ever, basically.
In my case, it was less intermittent events and more low-latency streaming data (position/GIS stuff), so I went with the forever frame. It really is splendid for pushing data to the browser without the nasty lag.
Comments
That's pretty much how I am, even with Comet stuff now too, though JS in general is better across browsers.
But really, for basic page layout, the rules around floats and position: relative and so-on really aren't that hard to remember.
In addition to memorizing the rules, you'll also memorize the specific IE bugs; see a page in IE all messed up, and be able to go, "Oh, I know what would cause that," and be able to fix it without spending hours tracking down the bug.
Woo!
Comet in IE6? Can you elaborate a bit? I recently had a need for a comet thingy (but not cross-browser compatibility) - so I made a small solution with x-mixed-replace. I don't even know where would I start with IE6, since even later versions are their own world.
Comet has worked since the old netscape days, it just wasn't called "comet" back then. Long polling works fine in IE6.
Long polling is possible in every browser ever, basically.
In my case, it was less intermittent events and more low-latency streaming data (position/GIS stuff), so I went with the forever frame. It really is splendid for pushing data to the browser without the nasty lag.