On Wed, Nov 4, 2015 at 8:02 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
> fantasai and I discussed this a bit today after reading Brad's email,
> and concluded that we did want to stick with just "start" and "end".
> Details:
>
> For today's simple 1-axis floats, "start" and "end" are unambiguous
> and simple, and consistent with text-align/etc.
>
Makes sense.
>
> In the future when we have 2-axis floats (as in the Page Floats
> module), 'float' can become a 2-value property, consistent with the
> proposals for background-position and scroll-snap-align. If you
> specify one value, it will duplicate to the second value (as normal
> for CSS). The default float-reference (inline) will only pay
> attention to the inline-axis value, so the extraneous block-axis value
> is ignored (similar to how scroll-snap-align only pays attention to
> the relevant axis). For the 2d float references (column, region,
> page), saying "float: start" will just put you in the start/start
> corner, which seems fine.
>
Ok, so "float: start" will mean that it floats to the start of the block
and start of the line, whereas "float: end" will mean it will float to the
end of the block and end of the line?
In most cases, page floats that float to the block start or end will
probably take up the entire length of the line, so that floating to the
start or end of the line will have the same effect. So the simplified
"float:start" will work fine for those cases.
But how about floating to the line start or line end with a float reference
of column, region or page and taking up 100% in the block direction? How
would the author specify that?
>
> ~TJ
>
>
--
Johannes Wilm
Fidus Writer
http://www.fiduswriter.org