[MeeGo-touch-dev] About parent style name selectors

[Stanislav Ionascu]

Hi,

Yes that's the intended behavior, as it works as when style is overriden based 
on parent, but this commit adds the support to also make use of the parent 
style name for that. 
To override the > 1st level children the '>' symbol is used. 
E.g. TestWidget > TestObjectStyle#StyleName. 

But it's not supported for the parent style name based selectors.

Best Regards,
Stanislav Ionascu

On Monday, September 20, 2010 05:26:01 pm ext Caio Marcelo de Oliveira Filho 
wrote:
> Hello,
> 
> looking at the commit 95b88f40ab97b640f9dca71c67a731d907be949e
> 
> http://meego.gitorious.org/meegotouch/libmeegotouch/commit/95b88f40ab97b640
> f9dca71c67a731d907be949e
> 
> it seems that it only considers the name of the direct parent, not of
> the other ascendants. Is that behavior intended?
> 
> For example, I modified the ft_mstylesheet_testobject.css a little
> bit, commenting the selector for "TestWidget2 TestObjectStyle". So in
> the last comparison of test_parent_stylenames, I was expecting to get
> attribute-color "#000100" (since our TestWidget is "Specialized"), but
> I get "#000010" instead.
> 
> ----8<---
> TestWidget TestObjectStyle
> {
>     attribute-color: #000010;
> }
> 
> /* TestWidget2 TestObjectStyle */
> /* { */
> /*     attribute-color: #000020; */
> /* } */
> 
> TestWidget#Specialized TestObjectStyle
> {
>     attribute-color: #000100;
> }
> 
> TestWidget3#Specialized TestObjectStyle#Specialized
> {
>     attribute-color: #000110;
> }
> --->8---
> 
> 
> By inspecting the code, it seems that only the stylename/objectname of
> the direct parent is considered. Is that the intended behavior?
> 
> 
> Cheers,