I might be assuming something that is not correct, so let me ask,
in the case of the train, what part is delegating to the navigationItem
renderer?
I'm assuming the af|train::link part.
So, regardless of the skinning syntax (af|train::stop::link or
af|train::stop af|train::link)
you would map
Oh, I see. Yeah, if the CSS generator break it that way, it would work.
However, that kind of behavior would have to be well documented to allow
developers to create new components because they would have no way to guess
that af|train::link (for example) is valid to use in the renderer code.
Simon Lessard wrote:
Hello all,
Well, at first I made it that way beause dual pseudo-element was
completely
removed because it was buggy.
yep, we never had keys with multi-pseudo-elements, so it wasn't written
to support it.
However, now that it was made that way I don't
dislike it.
