If you save a new style based off of Default, it correctly contains ONLY the properties you have changed.
However, if you create another style based off of a style you have already created, it contains too many properties and thus does not correctly inherit properties from default.
This occurs with theme Enlightened, and others - but NOT with Minimalist Theme.
Tested with fm15.0.2 on Mac (El Cap), but extremely probably in all platforms + versions since themes exist.
This, I think, is the reason:
How to recreate
See attached file, or:
- Create a layout with theme Enlightened
- Add Text object "Default" to layout
- Duplicate the text object and rename it to "Generation 1"
- Change the font-size to 48 pt
- Save this as a new style "Generation 1"
- Duplicate this object and rename it to "Generation 2"
- Save this as a new style "Generation 2"
- Now click the "Default" text and change the font to "Courier New"
- Save the changes to the Default style
I expect BOTH Generation 1 and Generation 2 to be displayed in "Courier New" (because I have defined the font in neither)
Generation 1 inherits the font-change from Default and is displayed in Courier
Generation 2, however, does NOT change and retains the old default font.
WHY does this occur?
There is a rogue semicolon (actually ";sans-serif") in the CSS font-family property of the default style.
Please see the attached file which is full of details.
Importance of this bug
- It breaks the one level cascadingness that we have in FM Themes!
- In custom themes already created and containing this bug (e.g. our print layout theme) it is impossible to adjust the style sheet to use the customers CI font by tweaking the Default style.
- It is bloating CSS-Stylesheets, spoiling performance in WAN and WebDirect
- It is very confusing to developers & another 'gotcha' in the themes and styles jungle.
Thanks for every improvement
MrWatson @ the FileMaker Conference 2016, Salzburg