[css3-flexbox] miscellaneous comments on Chapter 4. Flex Items from Kang-Hao (Kenny) Lu on 2012-07-06 (www-style@w3.org from July 2012) (original) (raw)

(12/07/06 15:19), Anton Prowse wrote:

On 04/07/2012 17:55, Kang-Hao (Kenny) Lu wrote:

17.4 Tables in the visual formatting model

The computed values of properties 'position', 'float',

'margin-*', 'top', 'right', 'bottom', and 'left' on the table

element are used on the table wrapper box and not the table

box; all other values of non-inheritable properties are used on

the table box and not the table wrapper box.

[snip] . I don't think there's any work to do in the case of an /anonymous/ table box, though, since no new properties can be specified on that box in the first place.

Yeah. I apologize for quoting a paragraph in css3-flexbox that's not actually relevant to my comment.

# Absolutely positioned children of a flex container are not
# themselves flex items, but they leave behind "placeholders" in
# their normal position in the box tree.

I am not sure what "normal position in the box tree" means here. Does it mean that the 'order' value on the absolutely positioned element would be propagated to the placeholder? Is this the only property in css3-flexbox that does this propagation for an abs-pos flex item? If so, I hope this is clarified.

I went with s/normal/hypothetical normal-flow/. Does that work?

I think my exact question is, for a case like

A B C

is the place holder before A or not? Or in other words, does the place holder has 'order: -1' or 'order: 0'?

Your s/// seems to suggest 'order: 0' but I think the wording is still a bit vague. The hypothetical non-flex normal flow would be "A placeholder C" but I think you want "C A placeholder" or "placeholder C A".

Indeed.

At this point, I am actually more interested in knowing the 'order' of the placeholder instead of saying again and again that I can't get the answer from the prose. The truth is, I still don't know.

Can someone tell me what 'order' does the placeholder in the above have? Can I safely say it's '0' now?

(Though I'd like to question if that's actually the behavior we want.)

Cheers, Keny

Received on Friday, 6 July 2012 07:57:38 UTC