|
Can you send me a simple
test case for this scenario so I can see if it is a bug or you are not implementing it correctly. What should be happening is we read the base skin in and merge in the skin extension after. The skin extensions css properties take precedence. They extend the base skin's properties. When we write out the css-2 stylesheet, we have a performance step where we group all the selectors with the same css properties together. This will then appear to be reordering the properties. Instead of the selectors being generated in the order you wrote them:
.af_foo {font-size: 8px; color: red; font-weight: bold; font-style: italic; font-family: Tahoma}
.af_bar {font-size: 12px; color: black; border-width: 1px}
.af_zoo {font-size: 8px; color: red; font-weight: bold; font-style: italic; font-family: Tahoma}
.af_xyz {color: red}
.af_abc {font-size: 12px; color: black; border-width: 1px}
You'll see them grouped together:
.af_foo, .af_zoo {font-size: 8px; color: red; font-weight: bold;font-style: italic; font-family: Tahoma}
.af_bar, .af_abc {font-size: 12px; color: black; border-width: 1px}
.af_xyz {color: red}
- Jeanne Cristi Toth wrote: My problem is even bigger :( |
- Re: [Trinidad] Skining - strange default value in: base-des... Jeanne Waldman
- [Trinidad] Skining - strange default value in: base-de... Cristi Toth
- Re: [Trinidad] Skining - strange default value in:... Simon Lessard
- Re: [Trinidad] Skining - strange default value... Cristi Toth
- Re: [Trinidad] Skining - strange default v... Simon Lessard
- Re: [Trinidad] Skining - strange defa... Jeanne Waldman
- Re: [Trinidad] Skining - strange default value... Jeanne Waldman
- Re: [Trinidad] Skining - strange default v... Simon Lessard
