search

w3c / css-houdini-drafts

Mirror of https://hg.css-houdini.org/drafts
https://drafts.css-houdini.org/
Other
1.84k stars 141 forks source link

[css-typed-om] Drop CSSPositionValue #817

Open tabatkins opened 6 years ago

tabatkins commented 6 years ago

CSSPositionValue is a leftover from the earliest drafts of Typed OM. It assumes that every position can be represented as a pair of physical offsets, but this is no longer true in B&B 4 (and <position> in general matches this, gaining three variant forms of offset pairs - physical, logical, and physical-axis-but-logical-direction). The type of position persists thru to computed values, so we can't even limit this to just computed values.

We just need to drop the class entirely for now, and reify the relevant properties as just CSSStyleValue, until we develop a proper position type.

css-meeting-bot commented 5 years ago

The Houdini Task Force just discussed Drop CSSPositionValue.

The full IRC log of that discussion <TabAtkins> Topic: Drop CSSPositionValue
<heycam> TabAtkins: CSSPositionValue was in the first draft
<heycam> ... assumes every position is a horiz/vert offset
<heycam> ... now they can be logicaly
<heycam> ... not certain how best to represent this flexibility in the object shape
<heycam> ... until I do I plan to drop it from the draft and impl
<heycam> github: https://github.com/w3c/css-houdini-drafts/issues/817
<heycam> TabAtkins: if anyone has ideas for representing these values would love help
<heycam> astearns: there have been a number of things we've dropped
<heycam> ... are we tracking those in any way?
<heycam> ... next level draft?
<heycam> TabAtkins: I shall soon
<heycam> ... we did a pub a while ago, need to do another one soon
<heycam> ... before EOY I'll get ready for a new draft
<heycam> ... and I'll have a substantial changes section to outline what happened
foolip commented 3 years ago

It was removed in https://github.com/w3c/css-houdini-drafts/commit/5261c1a323ea062d69cb5a3f1e69734fd176948a, this can be closed.

foolip commented 3 years ago

But it looks like no Chrome bug was ever filed. It's still in css_position_value.idl with no FIXME or anything.

graouts commented 1 year ago

Additionally, WPT still references this heavily and will produce noise when trying to determine how browsers do with this feature (assuming either Firefox or Safari end up enabling this feature).