Hi All,
I use Firefox only because of vBulletin's WYSIWYG doesn't work in Safari. Any plans to make this work ?
Regards,
.Joel
Hi All,
I use Firefox only because of vBulletin's WYSIWYG doesn't work in Safari. Any plans to make this work ?
Regards,
.Joel
Every time a new version of Safari is released we look again to see if it's ready and offers the power that IE and Firefox offer for WYSIWYG control. So far, it has proven not to be ready.
We have been doing the same with Opera and I'm happy to say that Opera is 99% of the way there, and there's a good chance that vBulletin 3.7 will allow Opera to use the WYSIWYG editor.
Kier, appreciate the response.
What is it that makes Safari not ready ?
Regards,
.Joel
Most likely its DOM and Javascript support aren't up to speed.As far as specifics go, Kier will have to help you.
Btw WYSIWYG can work in Opera, if you select "Mask as firefox".
Haven't tested it myself, a friend of mine who uses Opera fanatically told me so.
That's sad to hear. I was hoping for a new editor by 4.0... I still get constant cursor problems in Firefox. Like it never showing up when I first click in the box, disappearing while I type, disappearing when I hit "space" and then I can't see how many spaces there are between words if I don't keep track.
I know this has something to do with using an iFrame and from what I've seen in their bug tracker it was fixed, but I still get the problem all the time. (fixed for 3.0 maybe?).
So is the chance for a new editor at least pretty high by 4.0, even if you haven't worked it out yet?
Edit: Eek. I checked out the YUI RTE and I like it too.. that IS too bad, then.haha. I liked the insert image script, lets you choose image alignment right from the script and everything. Pretty laggy though, esp. when clicking through the different elements (p, li, etc).
Last edited by jw0ollard; Sun 18th Nov '07 at 3:42am.
Has the vBulletin team checked out Safari 3.1 for use with the WYSIWYG editor?
I'm browsing with Safari 3.1 right now - I will do WYSIWYG testing early next week.
I checked this out at the start of the 3.7 process to see how realistic it was to get Opera and Safari compatibility. The short answer is that our wysiwyg code is overly complicated and adding more browser specific sections would make it worse.
There wasn't a quick way to do it, I filed some bugs with Opera regarding there implementation and Webkit has some tracking ones.
Bookmarks