Flightcrew error or bad coding?

[Turtle91]

I saw that "subset" term as well but I couldn't find a list that defined which ones were/were not included in the subset - it just went on to section 3 where it said ALL pseudo elements/classes must be supported.

Do you know where that list could be found if there is such a beast?

[edit] ok now that I'm awake, let me clarify the drivel in my previous statement...
Jellby's reference on how ePub spec relates to CSS declares that the spec only requires a compliance with a subset of properties - and the link points to section 3 where it describes the subset of properties among the many tables. But the only reference I can see to selectors in section 3.1 is that ALL pseudo elements/classes MUST be included.

Is there a list that describes a subset of selectors??

[Jellby]

Yes, the intent is that all pseudo-elements should be supported:

http://www.daisy.org/epub/issues/sta...ements-unclear

[DiapDealer]

The only thing left to determine, then, is whether the "content" property is supported "officially" in ePub2.

Again... I'm not the guy who knows.

[Turtle91]

Nice wrench you threw into that train of argument Diap - I was on a roll!!

Of course "content" is supported in epub's - otherwise all we would have is structure and styling!!

However the "content property" appears in the required subset properties list ePub 2.01 under "Generated Content, Automatic Numbering, and Lists".

Strangely it has a note after it:

[9] Must not be used within a style sheet whose @media value is other than aural.

That obviously doesn't make sense if you are not using an aural style sheet, so I'm not sure why it would be in the Generated Content section instead of the Aural Stylesheet section???

I do know that the content property is described as part of the :before and :after pseudo elements in both CSS2.0 (section 11.1) and CSS2.1 (section 12.1-12.2):

The 'content' property, in conjunction with these pseudo-elements, specifies what is inserted.

It is saying that the content property is inherent in the use of the :before and :after elements...you can't define them without the content property.

If you ask me, that would seem to imply that if the pseudo-elements MUST be supported, then the content property MUST be included...

[Jellby]

... but only with @media aural...

[DiapDealer]

There you go.

But either way, Flightcrew probably shouldn't be giving it the old "This resource is present in the OPF <manifest>, but it's not reachable (it's unused)" yada-yada. If having manifested resources that are only referenced via CSS (not in any xhtml) is valid under any circumstances at all, it (Flightcrew) should probably understand that such resources are, in fact, being used.

[Turtle91]

Originally Posted by Jellby

... but only with @media aural...

That's what's so strange. All of the references of the content property are in OTHER sections - NOT in the aural style sheet section. If it was in the aural section it would make sense to say you can't use this anywhere else but an aural style sheet.
Its like describing the border property in a box model section and attaching a note saying you can't use border on anything but an aural style sheet...

Well, I'm definitely

Diap is right and the only thing we have a (small) chance of affecting is getting flightcrew to not flag it. That won't happen until Sigil is ePub 3 friendly. It passes ePubcheck3 and the "lackluster" devices/apps don't support it (surprise) while the good ones do....

Thanks for the discussion!

[DaleDe]

Originally Posted by Turtle91

Nice wrench you threw into that train of argument Diap - I was on a roll!!

Of course "content" is supported in epub's - otherwise all we would have is structure and styling!!

However the "content property" appears in the required subset properties list ePub 2.01 under "Generated Content, Automatic Numbering, and Lists".

Strangely it has a note after it:

That obviously doesn't make sense if you are not using an aural style sheet, so I'm not sure why it would be in the Generated Content section instead of the Aural Stylesheet section???

You are misinterpreting the text in the standard. If the CSS has no media section at all, which is the main case for most CSS files then it should be included.

Dale

[Turtle91]

Originally Posted by DaleDe

If the CSS has no media section at all, which is the main case for most CSS files then it should be included.
Dale

Just so I understand: If there is no @media declared at all then the note does NOT apply because the @media value is not "other than aural"...it is nothing?

If that is the case then that is a good thing.