[css3-gcpm] More feedback

6. Footnotes
s/traditions footnotes/traditions of footnotes/

6.4 Footnote calls

What should happen if a font is used with limited superscripted entries (or at least less than the number of footnotes)?

6.7 target-pull()

Clarification needed: Does target-pull() only refer to textual content (like named strings) or does it refer to an element and its descendents (like running headers/footers)?

6.9 Footnote magic

s/are automatically labeled with the value of ./are automatically labeled with the value of the footnote counter./

7. Named flows

Example XXXVIII (tablenote):-

It is implicit that the ::note-marker and the and the content of float: to(...) gets moved together to the named flow. So:-

s/On the 'float' property, 'to()' is introduced to indicate that the element should be pushed from its natural position and into a named flow./On the 'float' property, 'to()' is introduced to indicate that the element (and it's ::note-marker) should be pushed from its natural position and into a named flow./

Clarification: Does the floated element gets "promoted" to a display: block type?

Question: What prevents the use of ::marker rather than ::note-marker?

Also, if an element that is floated to a named flow does that include ::before, ::after content as well?

9. Hyphenation

The resources -- what format/specification do they adhere to?

11. Image resolution

Computed value: I think it should be a single value; at least the actual value used should be accessible through the CSSOM.

Should there also be a 'border-image-resolution' for completeness?

12. Page marks and bleed

page-bleed

s/<length/<length>/

14. CMYK colors

I understand that:

color: red
color: cmyk(...)

is backwards compatible; but I'm wondering if we can think of a more compact syntax:-

color: cmyk(...) || red

(inspired by the '||' operator).

Obviously this is not backwards compatible and would need to be proceeded with a color: red -- but if in the future we add another optionally supported colorspace then we specify it more compactly:

color: ycc(...) || cmyk(...) || red

Comments?

15. Page floats

Other keyworks -- should include to(...) for named flows.

'next' value -- s/next page/next page (or column -- depending on the reference keyword)/

16. Advanced multi-column layout

The text "Fractions on the 'gr' unit refer to the last distance added." confuses me. If I have 1.5gr and it's 1 column width + 1/2 a column gap -- it's not intuitive what the "last distance added" is. Not sure how to better word it.

Example LXXXI / float-offset:

Question: With a float-offset of 2gr I expected that (per 16.1) "the middle of the float should be aligned with the specified grid line (or portion thereof)." -- i.e. the middle of the float should be aligned with 2gr -- 2gr is the left edge of the 2nd column. It would seem if this example was to work (as spec'ed) we'd need float-offset: 2.5gr (middle of 2nd column). Example LXXXV is assuming this.

Another (artificial) example I'd like to know how to do is how to float an element just in the column gap?

float-offset: 1.5gr -- should do the trick for positioning
width: 1gr -- not clear which grid this is referring too?

I am thinking that perhaps it would be better for these advanced grid float cases if the CSS properties were more explicit:

float: left 2.5gr // align center with middle of 2nd column (counting from left)

float: left [2gr,3gr] // center float between grid line 2 and 3 (counting from left)
                      // (i.e. center in 2nd column); if width: auto then width is
                      // distance between grid line 2 and 3.

float: left 2.5gr top 50% // horz centered in 2nd column, vert centered

The [<length>,<length>] specifies an offset to determine the left & right side of the float; it also affects calculated 'width' if it is specified as 'auto' to be the distance between the two lengths.

This does solve my (artificial) problem from above:-

float: left [1gr,2gr] // float in 1st column gap; float width is same as column gap (assuming width: auto)

--

Since this email is getting rather long and I'd like to share my comments sooner rather than later I'll send the rest of my comments for css3-cgpm at a later date.

- Jacob

Received on Friday, 19 September 2008 04:13:05 UTC