W3C home > Mailing lists > Public > public-css-archive@w3.org > January 2017

Re: [csswg-drafts] [css-text-3] Don't mince words about aliasing/shorthands with word-wrap

From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
Date: Sat, 07 Jan 2017 02:32:55 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-271056827-1483756372-sysbot+gh@w3.org>
The wording is unintentionally loose, but the intent was to make it a 
shorthand. If we want to keep that, we should update the phrasing to:

> For legacy reasons, UAs must treat word-wrap as an alternate name 
for the overflow-wrap property by implementing it as a shorthand of 
overflow-wrap.

Some of the reasoning for that is documented here: 
https://wiki.csswg.org/ideas/aliasing

TL;DR: we had a reasonably extensive discussion about how aliasing 
should work when "aliasing" break-before and page-break-before, and 
figured that shorthands were a good way to do that: well defined 
(including the OM) without needing to introduce any new concept, 
generally well behaved, deals well with the case when the legacy prop 
and the new prop don't have the exact same set of values.

I still think the idea has merit to it, but if implementations 
generally agree on a different aliasing mechanism, we should spec it 
and use that. Spec-fiction doesn't help anyone. Maybe we can keep 
exceptions and use shorthands when the legacy prop and the new prop 
accept different values.

-- 
GitHub Notification of comment by frivoal
Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/866#issuecomment-271056827 
using your GitHub account
Received on Saturday, 7 January 2017 02:33:12 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:26:36 UTC