W3C home > Mailing lists > Public > public-fxtf-archive@w3.org > April 2017

Re: [fxtf-drafts] [motion] Should omitted <size> just extend to the containing block edge?

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Fri, 21 Apr 2017 05:56:06 +0000
To: public-fxtf-archive@w3.org
Message-ID: <issue_comment.created-296081748-1492754165-sysbot+gh@w3.org>
The CSS Working Group just discussed `https://github.com/w3c/fxtf-drafts/issues/73`.

<details><summary>The full IRC log of that discussion</summary>

<shane> Topic: https://github.com/w3c/fxtf-drafts/issues/73
<shane> Github Topic: https://github.com/w3c/fxtf-drafts/issues/73
<fantasai> ericwilligers, I think the proposal was to move <position> inside the ray() fuction and delete offset-position or add the none-based positioning feature to something else?
<TabAtkins> jihye: offset-based positioning properties describe tehe path the element is on, various ways
<TabAtkins> jihye: ray() defines a line segment starting from the position, going in the defined direction
<TabAtkins> jihye: It has 3 params - angle, size, contain.
<TabAtkins> jihye: size is where the path ends.
<TabAtkins> jihye: When talking about size, have to know the path length
<TabAtkins> jihye: To resolve %s
<TabAtkins> jihye: So most important factor is <angle> in ray(); I want consistency with %s here, so if all you do is animate the angle, the % resolves to the same length the whole time.
<TabAtkins> fantasai: So question is what the behavior is when you *omit* the size keyword.
<TabAtkins> fantasai: Earlier you just draw the ray until you hit an edge, it's that long.
<TabAtkins> fantasai: Current spec it defaults to closest-side.
<TabAtkins> fantasai: So my suggestion is adding an option (or defaulting it) to get back the "cast the ray to the edge of the box" behavior.
<TabAtkins> [explicitly unminuted discussion about whether it makes sense to be the default]
<TabAtkins> fantasai: It's not clear, fi the "measurement angle" is different from the angle you're actually using, why 100% stops at the given point.
<TabAtkins> shane: I think that's not usually the case - mostly it'll be used to position things around a circle around the box.
<ericwilligers> Can we make the <size> non-optional?
<TabAtkins> ChrisL: I agree with shane - i think it's usually the case that you're using this feature for polar-positioning multiple things.

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/73#issuecomment-296081748 using your GitHub account
Received on Friday, 21 April 2017 05:56:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 November 2018 00:45:57 UTC