Open Bug 1838746 (css-anchor-position-1) Opened 2 years ago Updated 2 hours ago

[META] [css-anchor-position-1] Implement CSS Anchor Positioning

Categories

(Core :: CSS Parsing and Computation, enhancement)

enhancement

Tracking

()

People

(Reporter: dholbert, Unassigned)

References

(Depends on 24 open bugs, Blocks 121 open bugs, )

Details

(5 keywords)

This bug tracks implementation of CSS Anchor Positioning Level 1.

Spec link: https://drafts.csswg.org/css-anchor-position-1/

See Also: → 1837502
See Also: → 1816760
Alias: css-anchor-position-1
Blocks: 1842698
Blocks: 1842703
Blocks: 1842114
Blocks: 1850104
Depends on: 1850829
Blocks: 1857653
Duplicate of this bug: 1863823
Depends on: 1865887
Depends on: 1875258
Depends on: 1877168
Depends on: 1877417
Depends on: 1881860
Blocks: 1881860
No longer depends on: 1881860
No longer blocks: 1881860
Depends on: 1881860
Depends on: 1882437
See Also: → 1885596
Blocks: 1867737
Blocks: 1895141
See Also: → popover
Blocks: 1897106
Blocks: 1897279
Blocks: 1897596
Keywords: dev-doc-needed
Depends on: 1900234
No longer depends on: 1897619
Depends on: 1908494
Depends on: 1906329
Depends on: 1909328
Depends on: 1909341
Depends on: 1909345
Depends on: 1909346
Depends on: 1909354
No longer depends on: 1908494

I see that this meta bug depends on a ticket about adding basic support in block layout, explicit excluding support in other layouts like flex and grid.
What is the plan for those other layouts ? Will the feature ship without support for them ? If yes, this will make feature detection harder in case the relevant support is for anchor positioning in a grid layout.

Flags: needinfo?(jwatt)

Those separations are just to provide some stepping stones to break up the implementation work into digestable parts. There's no intention to release those parts separately, and usable feature detection is something we'll very much be keeping in mind. If/when we get to the point that we're going to release something that will be noted here, whether or not it's a "complete" or partial release.

Flags: needinfo?(jwatt)
Depends on: 1911925
Depends on: 1917695
Depends on: 1920495
Blocks: 1920937
Depends on: 1923392
Depends on: 1923758
Depends on: 1923954
Depends on: 1924084
Depends on: 1924213
Blocks: 1911925
No longer depends on: 1911925
Blocks: 1917050
No longer depends on: 1917050
Blocks: 1920495
No longer depends on: 1920495
Blocks: 1906329
No longer depends on: 1906329
Depends on: 1924786
Depends on: 1924787
Depends on: 1924788
Depends on: 1924210
Depends on: 1925770
Depends on: 1925802
Depends on: 1925810
Depends on: 1925819
Blocks: 1925591
Blocks: 1925943

I noticed the spec specifically mentioned that transform and other post-layout effects will not affect the position of the anchors. Is there any plans to address this?

I noticed the spec specifically mentioned that transform and other post-layout effects will not affect the position of the anchors. Is there any plans to address this?

See this CSSWG issue: https://github.com/w3c/csswg-drafts/issues/8584 — if you have any specific use cases you're thinking about, please, comment in the issue, it will help with moving it forward!

Depends on: 1931935
Depends on: 1929380
Blocks: 1933967
Depends on: 1950201
Depends on: 1950251
Blocks: 1951910
Depends on: 1959416
Depends on: 1959421
Blocks: 1962487
Blocks: 1962074
Blocks: 1962017
Depends on: 1928128
Blocks: 1963512
Depends on: 1968745
Depends on: 1966524
Depends on: 1967755
Depends on: 1969350
Depends on: 1970240
Blocks: 1973949
Blocks: 1976614
Blocks: 1977088
Blocks: 1977917
Blocks: 1976354
Blocks: 1979986
Blocks: 1979911
Blocks: 1979593
Blocks: 1978980
Blocks: 1978736
Blocks: 1980278
Depends on: 1985654
Depends on: 1986554
Depends on: 1986919
Depends on: 1987916
Depends on: 1987917
Blocks: 1970240
No longer depends on: 1970240
Blocks: 1969350
No longer depends on: 1969350
Blocks: 1950201
No longer depends on: 1950201
Blocks: 1985302
No longer depends on: 1985302
Blocks: 1986919
No longer depends on: 1986919
Blocks: 1986090
No longer depends on: 1986090
Blocks: 1966524
No longer depends on: 1966524
Blocks: 1986554
No longer depends on: 1986554
Blocks: 1986132
No longer depends on: 1986132
Blocks: 1967755
No longer depends on: 1967755
Blocks: 1950251
No longer depends on: 1950251
Blocks: 1931935
No longer depends on: 1931935
Blocks: 1929380
No longer depends on: 1929380
Depends on: 1987926
Depends on: 1987930
Depends on: 1987943
Depends on: 1987946
Depends on: 1987947
Depends on: 1987954
No longer depends on: 1968745
Depends on: 1909339
Blocks: 1987931
Depends on: 1988038
Depends on: 1959187
Depends on: 1988224
Depends on: 1988225
Depends on: 1963090
Depends on: 1989292
Depends on: 1990069
Depends on: 1990901
Depends on: 1991211
Depends on: 1986602
Depends on: 1924792
Depends on: 1991710
Depends on: 1991968

Now that CSS Anchor Positioning Level 1 & Level 2 are both released (both technically in draft), could Firefox be one of the first to implement both specs.

Especially if this is an active effort, supporting both here would be a very big win for interoperability and for Firefox.

You need to log in before you can comment on or make changes to this bug.