Firefox 1.0 PR

[gregweller]

Is anyone here using it? And if so, are you having any problems posting?

Since I switched a couple of days ago from .93 to 1.0, I've noticed I can't get enhanced mode to work in the post window. I'm not getting a WYSIWYG preview as I'm typing, and so forth. I'm halfway to jumping back to the previous version. I haven't noticed anything different in the settings.

Could this be a Java or Javascript setting that needs changing, or have they changed the engine such that it no longer works the same?

I'm trying this with 1.0PR and I'm seeing the tags in enhanced mode, but to be honest with everyone, I guess I didn't realize that I wasn't supposed to . Let's see if cut and paste works:

Prior to upgrading to 1.0PR from 0.93, I could highlight text, and then click on the B, I or U icons, and have it apply that to the text. Now it shows tags, instead. I'm in enhanced mode, so that shouldn't be a problem. I've tried resetting it, to no avail. I'll try deleting my cookies for enworld. Perhaps that's the problem (although it wasn't before, when I went from .89 to .93, iirc)

That was a straight cut and paste and that seemed to work. I also bolded and italiced it, and that seemed to work. One thing that I have heard is that it's not a good idea to install a version of Firefox over another version of Firefox. Either delete the earlier version or install it in a completely different directory. I have a number of earlier versions installed on a USB drive (including a Chinese version that I've been using to test fonts), but I have them in different directories with different .bat files to start them--but they co-exist fine. Sorry I couldn't be more helpful, but there's nothing that I see that would want me to go back to IE.

 

[WizarDru]

If it still doesn't work, it's a bug.

Apparently, they made changes to the Useragent in 1.0, and that's the source of the problem with the WYSIWYG editor.

From the Vbulletin support boards:

http://www.vbulletin.com/forum/bugs.php?do=view&bugid=3373&status=60


So I'll keep searching for a workaround.