Re: [fxtf-drafts] [css-motion] offset-* property names collide with logical properties

The CSS Working Group just discussed `https://github.com/w3c/fxtf-drafts/issues/51`, and agreed to the following resolutions:

* `RESOLVED: #51 won't cause motion-path to rename; the offset-* logical props will change name.`

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

```
<shane> Topic: https://github.com/w3c/fxtf-drafts/issues/51
<shane> Github topic: https://github.com/w3c/fxtf-drafts/issues/51
<TabAtkins> shane: Offset property names collide with logical props.
<TabAtkins> shane: We have offset-path/rotation/etc. Logical props has offset-block/inline-start/end.
<TabAtkins> shane: Question is what the 'offset' shorthand do.
<fantasai> TabAtkins: I'm okay with no shorthand for positioning offsets
<fantasai> fantasai: It's a PITA to have to set tbrl to zer
<fantasai> fantasai: So we should have a shorthand for them
<TabAtkins> TabAtkins: If we can agree that the logical props dont' need a shorthand, we can just let the logical props to stay as they are, and give 'offset' to the motion-path spec.
<fantasai> fantasai: And that shorthand should match the prefixes (although it doesn't have to but that would be silly)
<TabAtkins> TabAtkins: If that's the case, then one of the impls has to change.
<TabAtkins> dbaron: I'm okay with changing logical prop name.
<TabAtkins> RESOLVED: #51 won't cause motion-path to rename; the offset-* logical props will change name.
<TabAtkins> [naming brainstorming]
<TabAtkins> position-*?
<TabAtkins> bounds-*
<TabAtkins> leaverou: What were the motion-path ones renamed in the first place? They're not really about offsets.
<TabAtkins> Florian: They'r enot about motion either - you only get that when you animation offset-distance.
```
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/51#issuecomment-296089562 using your GitHub account

Received on Friday, 21 April 2017 06:24:26 UTC