Skip to content

Inline size: remove 'number' value. - #482

Merged
Tavmjong merged 2 commits into
w3c:masterfrom
Tavmjong:inline-size
Jul 23, 2018
Merged

Tavmjong merged 2 commits into
w3c:masterfrom
Tavmjong:inline-size

Conversation

@Tavmjong

@Tavmjong Tavmjong commented Jul 5, 2018

Copy link
Copy Markdown
Contributor

Fixes #436

@Tavmjong
Tavmjong requested a review from ewilligers July 5, 2018 13:13
@ewilligers

Copy link
Copy Markdown
Contributor

Why isn't auto supported?

@Tavmjong
Tavmjong merged commit ed10b56 into w3c:master Jul 23, 2018
@Tavmjong

Copy link
Copy Markdown
Contributor Author

What would be the 'auto' value?

@ewilligers

Copy link
Copy Markdown
Contributor

We seem to have SVG and CSS defining inline-size in conflicting ways.

https://drafts.csswg.org/css-logical/#propdef-inline-size
supports 'auto' and has 'auto' as the initial value.

What would be the 'auto' value?

Discussed for HTML in https://www.w3.org/TR/CSS21/visudet.html#propdef-width

Perhaps the SVG spec needs to discuss it too.

I don't think we have any browser implementations following the SVG grammar. Blink supports 'auto' and has 'auto' as the initial value.

@AmeliaBR

Copy link
Copy Markdown
Contributor

@ewilligers Can you make a separate issue for this, since this PR has now been merged? auto should be allowed, and should be the default value, meaning do not constrain the inline size at all. Although that brings up the question of what the computed value should be: the text length, I guess.

There should maybe also be a note that says that the definition in CSS Logical Properties will supersede the SVG-specific one, when that spec is finalized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants