-
Posts
-
With the latest build I’m experiencing an issue I was reading about in an earlier version that appears to have resurfaced – custom class names in the Developer tab are being “cleansed” to lower-case such that Quick CSS names do not match up with chosen custom class names. (If I should not be experiencing this, please let me know… I did not see it in the list of changes to come, listed in the thread above.) Note that I do not even have to enter a new class name for the name to be text-transformed to lowercase, this is happening to existing class names too… as I use camel-case religiously this immediately breaks every custom class I’ve ever created on pretty much every site I’ve got.
As an example, while Quick CSS window I may have chosen outsideColumnFix as the class name, the element’s class name is being transformed to outsidecolumnfix and thus not being applied.
Please advise, thanks!
Can I get confirmation/acknowledgement that this issue is being looked at and/or if I shouldn’t be having this issue?
Hi,
Thank for the inquiry.
It is now required to use lowercase in the custom css class field unless you’re using the “avf_save_string_translated” filter to return the unmodified version of the class name. Usage example can be found in the following link.
Related thread: https://kriesi.at/support/topic/4-6-update-doesnt-recognize-old-custom-css-class/page/3/#post-1144934
And according to the following style guides, it’s not recommended to use capital letters in your class or id names — always use lowercase.
// https://google.github.io/styleguide/htmlcssguide.html#ID_and_Class_Naming
// http://jonrohan.codes/styleguide/css-selectors.htmlOf course, it’s not a rule but it is always advantageous to follow such guides.
Best regards,
Ismael
- You must be logged in to reply to this topic.