W3C home > Mailing lists > Public > www-style@w3.org > March 2015

[css-ui] review of the latest batch of edits and suggested tweaks

From: Florian Rivoal <florian@rivoal.net>
Date: Wed, 4 Mar 2015 15:16:34 +0100
Message-Id: <F1A1C6C5-56E1-445D-A757-0BD1B5DC7E9E@rivoal.net>
Cc: Tantek Çelik <tantek@cs.stanford.edu>
To: www-style list <www-style@w3.org>
Hi Tantek,

Thanks for the latest edits, the spec is in pretty good shape, with almost all issues resolved now.

I've made a quick review of your commit, and here are my comments:

=== resize property ===
See this mail:

=== text-overflow ===

> Note: The "[...] its block container element" detail of the "clip" value definition is at risk pending implementation and potentially web compatibility feedback.

I don't think the note and the "at risk" are needed, since that is the legacy behavior that everybody implements since forever (including browsers that don't support the text-overflow property, since ''clip'' is the default value).

=== cursor ===

> The cursor property does not apply over native user-agent controls such as scrollbars, resizers, or other native UI widgets e.g. those that may be used inside some user agent specific implementations of form elements.

I'd go with "UAs may ignore the cursor property" rather than "The cursor property does not apply". We want to allow UAs to display whatever cursor they deem appropriate over these controls, but there is no need to forbid them from paying attention to the cursor property if they don't have any particular cursor they want to display.

> +Ignored Terms: text
> +Ignored Terms: default
> [...]
> +context, specifically: auto behaves as 'text' over text, and 'default' otherwise.

The correct bikeshed markup is ''cursor/text'' and ''cursor/default'' rather than 'text' and 'default', and once you write it that way, you can drop the ignored terms.

 - Florian
Received on Wednesday, 4 March 2015 14:16:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:52 UTC