Posted by norislee on July 24, 2009 at 4:46pm
5 followers
Jump to:
| Project: | OpenWYSIWYG Editor |
| Version: | 6.x-1.0-rc1 |
| Component: | User interface |
| Category: | bug report |
| Priority: | normal |
| Assigned: | fidokomik |
| Status: | active |
Issue Summary
Will this be Chrome browser compatible in future releases?
Thanks,
MTG
Comments
#1
Good question. Now that it's 2010, it should be a good time to revisit this issue, right?
#2
Until it gets officialy supported you can coment out the validation and return always true, under your own risk.
File: openwysiwyg.modified.js
Line: 1850.
/*** Determine if the browser version is compatible
*
* @return true/false depending on compatiblity of the browser
*/
isBrowserCompatible: function() {
// Validate browser and compatiblity
//if ((navigator.userAgent.indexOf('Safari') != -1 ) || !document.getElementById || !document.designMode){
if (!document.getElementById || !document.designMode){
//no designMode (Safari lies)
return false;
}
return true;
},
#3
Workaround found ;-)
isBrowserCompatible: function() {
// Validate browser and compatiblity
if ((navigator.userAgent.indexOf('Safari') != -1 && navigator.userAgent.indexOf('Chrome') == -1) || !document.getElementById || !document.designMode){
//no designMode (Safari lies)
return false;
}
return true;
},
#4
I tested fidokomiks patch, it works perfectly (under Chromium 8.0.552.215 (67652) under Ubuntu 10.10).
IMHO you should include that patch into HEAD before you release 6.x-1.0!
Chrome/Chromium is a good browser, and nowadays has not any more the bad Javascript implementation of those days when you excluded it!