Firefox 3.6 has a bug reported that effects document.readyState. So the current patch for ktml's toolbar not showing buttons may be redundant after the bug is addressed.
https://bugzilla.mozilla.org/show_bug.cgi?id=300992
Also, check out the dev notes for FF 3.6:
https://developer.mozilla.org/en/Firefo ... developers
You'll notice some changes to DOM handling that will effect uilities.js. getBoxObjectFor() has been removed; it has 3 instances in utilities.js and one instance in editor_mozilla.js. So more trouble there.
I believe the toolbar button bug will right its self after a subversion release of 3.6. This should also right the related css style drop menu bug.
Firefox 3.6 Quirks
Re: Firefox 3.6 Quirks
After a little more research, I believe getBoundingClientRect() is a potential replacement for getBoxObjectFor().
Re: Firefox 3.6 Quirks
Hi v2Media and welcome to the very busy forum. 
Thanks for that input and well spotted on the dev notes.
Did you try to replace the getBoxObjectFor() with getBoundingClientRect() to see if it works?
I might give it a go this week coming but my java is not the best so I guarantee nothing.
What do you think the issue might be with the insert table button?.
Thanks for that input and well spotted on the dev notes.
Did you try to replace the getBoxObjectFor() with getBoundingClientRect() to see if it works?
I might give it a go this week coming but my java is not the best so I guarantee nothing.
What do you think the issue might be with the insert table button?.
Re: Firefox 3.6 Quirks
Hi Fred, the forum is a very good idea 
I don't care how active it is. Should the interakt site go down, this'll be the place for extending the life of these products. I'm only concerned with KTML though. It's 3 years since Interakt dropped the product and still there's nothing comparible on the market; it's still the best. I have A LOT of clients using the product, so I have to ensure it works until their sites' get upgraded.
No idea on the table bug. I think the best approach is to refactor the portions of code that FF3.6's new JS engine doesn't support. By taking that approach, the bugs should right themselves. I hope to tackle this over the next few weeks.
Since 3.6 has a bug with readyState(), I'm advising clients to downgrade to FF3.5.X
I don't care how active it is. Should the interakt site go down, this'll be the place for extending the life of these products. I'm only concerned with KTML though. It's 3 years since Interakt dropped the product and still there's nothing comparible on the market; it's still the best. I have A LOT of clients using the product, so I have to ensure it works until their sites' get upgraded.No idea on the table bug. I think the best approach is to refactor the portions of code that FF3.6's new JS engine doesn't support. By taking that approach, the bugs should right themselves. I hope to tackle this over the next few weeks.
Since 3.6 has a bug with readyState(), I'm advising clients to downgrade to FF3.5.X
Re: Firefox 3.6 Quirks
I have the same "problem" and I can't see how the problem can be solved, as you said there is none better.v2Media wrote:I have A LOT of clients using the product, so I have to ensure it works until their sites' get upgraded.
I will just have to make it work for as long as possible.
Looking forward to your input.
Re: Firefox 3.6 Quirks
Is it my imagination or is Firefox 4 BETA working with KTML again?
KTML in the old interakt site is functional again.
Or maybe they used our patches to fix it.
KTML in the old interakt site is functional again.
Or maybe they used our patches to fix it.