Closed (fixed)
Project:
Wysiwyg
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
6 Mar 2007 at 17:04 UTC
Updated:
26 Sep 2008 at 20:21 UTC
Jump to comment: Most recent file
TinyMCE is not generating a warning when loading in Safari - even thought the safari warning option has been set.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | wysiwyg.safari.patch | 2.94 KB | sun |
Comments
Comment #1
johnalbinAs a Safari user, I implore you to NOT enable the warning. If you do, your site will be unusable for Safari users, as they will see a javascript dialog box on EVERY page. IMO, this Safari warning is a huge bug in TinyMCE (the editor code, not the Drupal module).
If the TinyMCE module is forcibly turning off the Safari warning, it's doing you a huge favor.
The right solution may be to disable the TinyMCE editor for Safari users. Which I believe is an option in the TinyMCE editor configuration (again, the editor code, not the Drupal module.)
Comment #2
AdrianB commentedI think it would be best if there was an option in the module to disable TinyMCE for Safari users and then use the filtered html input filter istead of the rich text filter. But I don't know if that's possible.
Comment #3
jpsalter commentedJohnAlbin and AdrianB - thank you for your input and clarifications.
1) Yes, it would be preferable to have TinyMCE turn off in Safari, but the option is not available in tinymce.module
2) Without this option - TinyMCE loads in Safari but does not work correctly - without the warning Safari users struggle and assume they are doing something wrong
3) Safari users need to be warned of this situation
Restating the bug: when the Safari warning option is set in the tinymce.module the Safari warning does not appear in TinyMCE when loaded in Safari.
Changing from "by design" -> "active"
Comment #4
johnalbinGood news! The latest 2.1.0 version of the TinyMCE editor no longer includes the god-awful
safari_warningalert box. (So, obviously, the safari warning option inside the TinyMCE module needs to be removed.)The new version may be more compatible with Safari (see http://wiki.moxiecode.com/index.php/TinyMCE:Compatibility ). That page says it “works "okay".”
I haven‘t the time today to test the new 2.1.0 version with Safari. Can someone report back?
The only other option is to disable TinyMCE entirely for Safari using the
browsersattribute insidetinyMCE.init().Comment #5
jpsalter commentedThis is good news. I'll install, test, and report back.
The instructions to disable TinyMCE for Safari is here:
http://wiki.moxiecode.com/index.php/TinyMCE:Configuration/browsers
Comment #6
sunComment #7
sunCommitted attached patch, which removes the editor configuration option and value.
Comment #8
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.