No. I think it was the “>” operator which didn’t work, but I don’t remember for sure.
> On Feb 11, 2018, at 1:53 PM, Piotr Zarzycki <[email protected]> wrote: > > Hi Harbs, > > Are you saying that without this namespace following situation didn't work? > > .myCss { > } > > .myCss .newCss { > } > > Thanks, > Piotr > > On Sun, Feb 11, 2018, 10:27 Gabe Harbs <[email protected]> wrote: > >> If it could work on Express, even better, but my impression was that the >> structure was going to have to change pretty significantly in some cases to >> get the theming to work. >> >> Harbs >> >>> On Feb 11, 2018, at 11:23 AM, Carlos Rovira <[email protected]> >> wrote: >>> >>> Hi, >>> >>> I think CSS vars would be a good addition although IE still doesn't >> handle >>> it. >>> >>> But in the other hand the Alex proposal seems to fit perfectly with what >> I >>> want to do. >>> >>> I didn't know that we have "-theme=" compiler option, and I think I will >>> use that extensively >>> >>> My last thought about all of this is if I should make this work on >> Express >>> instead of creating a complete new UI set (Vivid) >>> >>> thanks! >>> >>> >>> >>> 2018-02-11 9:53 GMT+01:00 Gabe Harbs <[email protected]>: >>> >>>> I don’t remember the details, but I’ve had css which would not compile >>>> until I specified the html namespace. It might have been using descender >>>> selectors. Not sure. >>>> >>>> Harbs >>>> >>>>> On Feb 11, 2018, at 9:20 AM, Alex Harui <[email protected]> >>>> wrote: >>>>> >>>>> I'm not clear how namespace would help. >>>> >>>> >>> >>> >>> -- >>> Carlos Rovira >>> http://about.me/carlosrovira >> >>
