Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
CSSPositionValue normalization should not imply parsing
Fixes #601
  • Loading branch information
nainar authored Jan 30, 2018
commit 763f470d72002928aa2fe5647b25203d12b54bc2
6 changes: 3 additions & 3 deletions css-typed-om/Overview.bs
Original file line number Diff line number Diff line change
Expand Up @@ -2789,9 +2789,9 @@ while CSS <<transform-function>> values become {{CSSTransformComponent}}s.
{{CSSPositionValue}} normalization {#positionvalue-normalization}
-----------------------------------------------------------------

If the provided value matches the <<position>> production, then a {{CSSPositionValue}} is constructed
with <var>x</var> and <var>y</var> components determined via the following process. If this process, or
any sub-process referenced by this process fails, then normalization as a whole fails.
CSS <<position>> values become {{CSSPositionValue}}s in the Typed OM, with <var>x</var> and <var>y</var>
components determined via the following process. If this process, or any sub-process referenced by this
process fails, then normalization as a whole fails.

1. Initialize both <var>x</var> and <var>y</var> to a {{CSSNumericValue}} value representing 50%.
1. If the provided value is a single keyword, length, percentage, or calc expression, then follow
Expand Down