Skip to content

[css-display][css-lists] Is a markerly positioned box out-of-flow? #1458

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
Loirooriol opened this issue May 23, 2017 · 1 comment
Closed

[css-display][css-lists] Is a markerly positioned box out-of-flow? #1458

Loirooriol opened this issue May 23, 2017 · 1 comment
Labels
Closed Accepted as Obvious Bugfix css-display-3 Current Work css-lists-3 Current Work Tracked in DoC

Comments

@Loirooriol
Copy link
Contributor

CSS Lists introduces position: marker, and it says

An element with position: marker counts as absolutely positioned.

However, CSS Display says

A box is out-of-flow if it is floated (via float) or absolutely-positioned (via absolute or fixed positioning).

It does not mention marker despite including fixed, which also counts as counts as absolutely positioned.

Is marker out-of-flow or not?
@tabatkins tabatkins added css-display-3 Current Work css-lists-3 Current Work labels May 25, 2017
@tabatkins
Copy link
Member

tabatkins commented Jul 5, 2017 •
edited by fantasai
Loading

It's out-of-flow, yes. We're just being overly specific in Display and tying the concept to specific values rather than the general concept. We'll remove that and just say that it's "via position"

triple-underscore added a commit to triple-underscore/triple-underscore.github.io that referenced this issue Jul 6, 2017
@triple-underscore
[css-display] 各種更新
e931519 
Commits on Jul 6, 2017

Note that 'display: contents' does not affect property inheritance.
Fixes w3c/csswg-drafts#1473
w3c/csswg-drafts@356b3296d5b20e00bedbfa8d1db59
d005a73bfc9

Normatively define what was in the previous note: that run-in fixup
occurs before first line determination.
w3c/csswg-drafts@37c01a4ef94aec7c352c3dc7c5cfc
31f8898ed4d

Move computed value bullet before box generation bullet.
w3c/csswg-drafts@5d10db8d8665f52994530304f2ddc
88236d37ccb

Clarify that run-in fixup occurs before block/inline fixup.
w3c/csswg-drafts@6f6913e20851f50ad81ca3cb43a49
9c01e8b2186

Expand out informal definitions of BFC.
Also fixes w3c/csswg-drafts#1471 .
w3c/csswg-drafts@388b1fb3bfa7dbe2ed112581322d2
a10787c9121

Refer to 'flow layout' directly, rather than just mentioning the types
of boxes that flow layout can produce.
Fixes w3c/csswg-drafts#1470 .
w3c/csswg-drafts@09212af80e10e4e3e57965bb27b2d
e3fdcd86e06

Make the run-in recursion explicit, so it's clear the second step
doesn't recurse.
Fixes w3c/csswg-drafts#1460 .
w3c/csswg-drafts@c9f1bb16d0e5077b9bca7027a7d72
52eeff5abf1

Be a little looser about what counts as abspos, because css-lists
defines as out-of-flow.
Fixes w3c/csswg-drafts#1458
w3c/csswg-drafts@f7ff60660c3b5e1b31000ffa0f729
ba04f13a2f8

Remove the w3c/csswg-drafts#1390 inline issue.
w3c/csswg-drafts@4514b3e7f2f0aa8ef95a84c107fb9
90fc2def209

Add note about the two categories of box-tree fixup, and their relative
ordering.
Fixes w3c/csswg-drafts#1355 .
w3c/csswg-drafts@f5b79e99bb8fc9ebea4ed956ed342
0bc69b90786

Apply diff, per resolution.
Fixes w3c/csswg-drafts#1118 .
w3c/csswg-drafts@dbb7042481d132efcb6869ecbdf44
f338d8ad944
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Closed Accepted as Obvious Bugfix css-display-3 Current Work css-lists-3 Current Work Tracked in DoC
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tabatkins @fantasai @Loirooriol