- From: Brad Kemper <brad.kemper@gmail.com>
- Date: Mon, 24 Nov 2014 07:14:24 -0800
- To: Jirka Kosek <jirka@kosek.cz>
- Cc: Liam R E Quin <liam@w3.org>, www-style list <www-style@w3.org>, Dave Cramer <Dave.Cramer@hbgusa.com>
On Nov 24, 2014, at 6:31 AM, Jirka Kosek <jirka@kosek.cz> wrote: > > On 24.11.2014 15:09, Brad Kemper wrote: >>> You can't solve more complex scenarious without such feature. There >>> are existing non-browser implementations that has to support this >> >> I'm not sure I know what you are referring to when you say "such a >> feature" and "this". Do you mean putting the selector into the >> function itself is necessary, instead of using the selector to the >> left of the declaration list with a different syntax? Or the other >> way around? > > Yes, what's CSS is missing is ability to use more expressive selection > mechanism for content property. OK. Did you think my 'copy-to' proposal on Saturday helped with that? I had ways to target a selected element's text, or the entire element, or all its child nodes, or an attribute or counter, for inclusion in 'content'. Is that still not expressive enough? >> Let's leave XPath support to a different thread. > > I was not proposing using XPath, this was just example. I expect that > selectors will be used. > > -- > ------------------------------------------------------------------ > Jirka Kosek e-mail: jirka@kosek.cz http://xmlguru.cz > ------------------------------------------------------------------ > Professional XML and Web consulting and training services > DocBook/DITA customization, custom XSLT/XSL-FO document processing > ------------------------------------------------------------------ > OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. > ------------------------------------------------------------------ > Bringing you XML Prague conference http://xmlprague.cz > ------------------------------------------------------------------ >
Received on Monday, 24 November 2014 15:14:53 UTC