Okay, so this all goes back to how Freeway handles CSS on a master page. The master pages create classes instead of ID’s which then get applied to any item on a page using the same settings as the master.
This works fine and dandy UNTIL you need to set a class for a item that’s referencing the master. If I use the Add Selector action or the extended dialog to create the class, it removes the existing class, and the item looses all styling.
I know you’re busy Walter, but is there a way for your action to add a class without removing the existing classes, or does anybody know of a workaround?
The code I posted on ActionsForge does not remove any existing classname. If there is no classname, then it will create one, if there is an existing one, it will append the new one. You can have lots of different classnames on a single element, as long as you aren’t concerned with IE 6 seeing “page salad”. (IE 6 will apply the first classname and ignore the rest.)
Walter
On Feb 8, 2013, at 2:23 PM, Caleb Grove wrote:
Okay, so this all goes back to how Freeway handles CSS on a master page. The master pages create classes instead of ID’s which then get applied to any item on a page using the same settings as the master.
This works fine and dandy UNTIL you need to set a class for a item that’s referencing the master. If I use the Add Selector action or the extended dialog to create the class, it removes the existing class, and the item looses all styling.
I know you’re busy Walter, but is there a way for your action to add a class without removing the existing classes, or does anybody know of a workaround?