The BaseHref property stopped working in 2.0FC and newer
"The editor now uses the same method used on version RC2 to load its contents on Gecko. It is now possible to have more than one editor in the page. This change has a negative impact: the BaseHref property is not working."
In the latest (2.2.1) FCKEditor release, that property is still not working. Is it ever going to be fixed, or is it better to pretend like it never existed and move on?
"The editor now uses the same method used on version RC2 to load its contents on Gecko. It is now possible to have more than one editor in the page. This change has a negative impact: the BaseHref property is not working."
In the latest (2.2.1) FCKEditor release, that property is still not working. Is it ever going to be fixed, or is it better to pretend like it never existed and move on?
RE: Is BaseHref broken forever?
We hope that the upcoming version of Firefox will fix it (and it probably will), so we can bring the BaseHref feature back to it.
Frederico Knabben
CKEditor Project Lead and CKSource Owner
--
Follow us on: Twitter | Facebook | Google+ | LinkedIn
RE: Is BaseHref broken forever?
Hi Frederico
The upcoming version of Firefox is already here as only big bad bugs will be fixed, if the problem you talk about is still present here: http://www.mozilla.org/projects/firefox/ then it won't be fixed in the final 1.5 release.
Can you give us a bug number in bugzilla or a better understanding about how to test ourselves if the problem is still present?
Thanks
RE: Is BaseHref broken forever?
I just did some tests with Firefox 1.5 Beta 1 and it seams that those problems have been fixed... so, we'll probably have it working for it in a future version...
What to do with older versions of Firefox? Force the update, or duplicate the code for compatibility (what a sad choice!)
Thanks for your comments.
Frederico Knabben
CKEditor Project Lead and CKSource Owner
--
Follow us on: Twitter | Facebook | Google+ | LinkedIn
RE: Is BaseHref broken forever?
Currently not too many people is using firefox and forcing them to upgrade I think that it's a good move for everybody, there are tons of fixes between 1.0.7 and 1.5.
Stating that from now on FCKEditor won't be fully compatible with Firefox<1.5 is a hard move, so I don't think that this is sensible. But I don't think that this is the only bug fixed in 1.5, many people have stated problems with the History button that are fixed in the new firefox and as I stated in another thread the comment that FCKToolbarStyleCombo.prototype.RefreshVisibleItems blocks in Gecko doesn't apply for me and I've been testing this setup for several days.
If we would be talking about a software that has special hardware requirements like a new GFx Card or a new Windows the thing would be different, but Firefox is free and so anyone who uses should be using the latest version as soon as possible.