WYSIWYG in Firefox bug, please apply the fix
 

Firefox 1.0 PR doesnt show WYSIWYG, because vBulletin understand version differently.

Please apply the fix publish here on vBulletin.org, so we (who use Firefox 0.10) can use WYSIWYG

http://www.vbulletin.com/forum/bugs....iew&bugid=3373


Look for:
Add bellow

Better yet, use a Release Candidate of Firefox 1.0 instead of the PR.

If you don't want to look for it, here's a link. 1.0 RC2 - looks like it was released November 4.

http://ftp.mozilla.org/pub/mozilla.o...p%201.0rc2.exe

I am sure he means it's a bug and can be considered a security hole though. :)

talking about bugs, I installed the scrolling news text hack, and fireworks displays it from left to right! That browser must have been made for Chinese, Arabs etc...

Cool, I didn't know RC2 was out. Im still on RC1 ;)

Cheers :)


BOT: I still recommend applying the fix, theres some people who dont want to use RC's but will wait for the final. (Just look at vB3 RC's...not everyone jumped on them did they ;))

Uhh that's how a marquee tag is supposed to scroll? You can always change the direction :)

Or... better still... make the following change so that all sites visited appear correctly...

Type in the Address Bar: about:config
Amend the value general.useragent.vendorSub to 1.0

:)

are you joking? a marquee is fom right to left. Changing the direction will make IE reverse it.

what exacly is getting fixed? I'm a FF user but i don't use or like the WYSIWYG editor.

Mozilla Corp, made a stupid move IMO anyway, in the PR/RC stages the Useragent reads as

0.10.X which vBulletin sees as 0.1 by default, which it is if you think about it. So the wysiwyg is only designed to work on FF .6 + not .1 ;) this changes it to work with .10 :)

My useragent reads as 1.0RC2 from install :)
And you cant spec moz to think "oh, vB's WYS is not designed to work with this useragent, we cant use it!", specially since they use *shrugs* phpBB for their forums. ;)

Only the PR is named 0.10 (the latest release is 0.10.1). The release candidates show up as 1.0RC (or 1.0RC2).

Bug yes, security hole no.

Honestly don't know if its worth applying the fix for a non-stable browser anyway, and seeing has the new version of firefox works correctly with the old code now. If you still want to run the PR you can always fix it from your end by changing the useragent.

Well firefox 1.0 is released Nov. 9 so it will no longer be a bug

i love problems which fix themselves ^^

Yep, definately something worth staying up way past midnight for. :D Not as much as vB3 was, but ;)

Im using 1.0 Final now :D
Mozilla was loading really really slow, I think their site got overloaded XD

they actually had firefox 1.0 released when i made the post (always check their ftp site)