W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2018

Re: [csswg-drafts] [cssom-view] Doubts regarding the overflow directions description

From: hyojin via GitHub <sysbot+gh@w3.org>
Date: Wed, 18 Jul 2018 11:56:01 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-405905260-1531914959-sysbot+gh@w3.org>
The change([89e5017](https://github.com/dbaron/csswg-drafts/commit/89e5017fa983ea69ebf8db044a3f7b64140ad3b2)) makes it clear in terms of solving a problem of the confusing terminology.

In the [`CSSOM View`](https://drafts.csswg.org/cssom-view) spec, on the other hands, the `{up, right, down, left}-ward` terms are used in several contexts to mainly describe how scrolling behavior works according to the scrolling box's overflow direction. So if we want to remove the terms as a physical direction, several statements including `*-ward` seems to be rephrased. (When I search 'ward' in the document, I can see the corresponding terms more than fifty in the CSSOM View spec.)

Alternatively, we could consider to revise the description of the six cases for two overflow directions (`{left|right}-ward` and `{up|down}-ward`) depending on the viewport’s or element’s block flow direction and inline base direction. If we apply a factor of `line-orientation` to the description in addition to the existing two factors such as `block flow direction` and `inline base direction`, it makes clear for describing the exact terminology. It seems a intuitive way for understanding the meaning of the conditions, but the css-writing-mode spec describes as follows: (see [the original text](https://drafts.csswg.org/css-writing-modes-4/#horizontal-block-flow))

> To avoid confusion, CSS specifications avoid using the set of of terms, {up, right, down, left}-ward.

-- 
GitHub Notification of comment by anawhj
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1569#issuecomment-405905260 using your GitHub account
Received on Wednesday, 18 July 2018 11:56:39 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 18 July 2018 11:56:42 UTC