Bleeding time on the cutting edge

I’ve spent most of the morning cleaning up some javascript classes to finish off IP Dynamic’s menu feature(s) and to try and find out why Firefox is freaking out when I load up the page content form.

To make the form cleaner, I’ve introduced a tabbed form concept which (via correctly marking up the HTML and using my tab-factory javascript class) allows the form to be broken up into different tabs.

This was going perfectly well until I stumbled across a rather odd javascript / Firefox bug. I’m using Firefox 1.5 RC 1 mainly because of the ability to re-order tabs and cleaned up dialogue boxes. Overall it’s a great release, but there are a few oddities (and it’s to be expected as it is only a release candidate).

One of these oddities has to do with Mozilla’s Midas engine (enableDesignMode) and changing the “display” attribute of a parent DIV after designMode has been enabled. The result is hard to explain, so here’s a little movie.

The fix was fairly straightforward (wrap the form with a DIV that has “display:block” set) but finding out what was the problem has cost me a morning.

IPD Gone Bad 132k Quicktime .Mov(ie)

Odd bugs yep. Personnally I rather prefer modifying the “className” attribute in Javascript as it’s more flexible and following the separation between contents & design (design in css, content in JS). Good luck.

donot know what the movie show.

I’m asumming the constant reloading of the tab.

That’ll be five points to Wilko.

*
To prove that you're not a bot, enter this code
Anti-Spam Image