Editing with Safari 5.1 & Chrome 13 removes case of CSS Styles
Permalink 1 user found helpful
I am not sure if this is a Concrete5, TinyMCE or Safari/Chrome/Webkit issue.
Safari 5.1 and Chrome 13 remove the case of identifiers of styles from the CSS when generating the "Style" drop down menu in the TinyMCE block editor.
If a class in the typography.css is called "H1-Web-small", then Safari 5.1 and Chrome 13 extract this from the CSS and show it as "h1-web-small". When the style is applied by choosing it from the Styles menu, the class h1-web-small is applied.
Safari and Chrome should not be changing the case of the style identifier when generating the Styles menu.
This issue is not present in Safari 5.0.x, nor in Firefox. They display and apply styles with the correct case.
I have attached an image of the Styles menu from both Firefox and Safari 5.1.
Safari 5.1 and Chrome 13 remove the case of identifiers of styles from the CSS when generating the "Style" drop down menu in the TinyMCE block editor.
If a class in the typography.css is called "H1-Web-small", then Safari 5.1 and Chrome 13 extract this from the CSS and show it as "h1-web-small". When the style is applied by choosing it from the Styles menu, the class h1-web-small is applied.
Safari and Chrome should not be changing the case of the style identifier when generating the Styles menu.
This issue is not present in Safari 5.0.x, nor in Firefox. They display and apply styles with the correct case.
I have attached an image of the Styles menu from both Firefox and Safari 5.1.
After more testing this is a TinyMCE issue.
It is present in the latest TinyMCE and occurs independently of Concrete5.
I have created a bug with TinyMCE.http://www.tinymce.com/develop/bugtracker_view.php?id=4649...
It is present in the latest TinyMCE and occurs independently of Concrete5.
I have created a bug with TinyMCE.http://www.tinymce.com/develop/bugtracker_view.php?id=4649...
from the TinyMCE Developers regarding this issue:
"This one seems impossible to fix at the moment. Since the folks at WebKit said it was to hard to maintain the case in the styleRules collections. So use hard coded styles until we make our own CSS parser not sure if that is something we want to do since the CSS specs are moving along way fast these days." Spocke.http://www.tinymce.com/develop/bugtracker_view.php?id=4649...
So make sure your css styles don't have upper-case identifiers.
"This one seems impossible to fix at the moment. Since the folks at WebKit said it was to hard to maintain the case in the styleRules collections. So use hard coded styles until we make our own CSS parser not sure if that is something we want to do since the CSS specs are moving along way fast these days." Spocke.http://www.tinymce.com/develop/bugtracker_view.php?id=4649...
So make sure your css styles don't have upper-case identifiers.
Is any one else seeing the issue?