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

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

From: Tantek Çelik <tantek@cs.stanford.edu>
Date: Wed, 4 Mar 2015 10:00:41 -0800
Message-ID: <CAEV2_WbXRsCu0XwLV6worehmrTDGdpax+nGRwchbRCTY5uP5hQ@mail.gmail.com>
To: Florian Rivoal <florian@rivoal.net>
Cc: www-style list <www-style@w3.org>, Tantek Çelik <tantek@cs.stanford.edu>
FYI edits to take into account suggested changes were made this
morning and are already in the draft.

On Wed, Mar 4, 2015 at 6:16 AM, Florian Rivoal <florian@rivoal.net> wrote:
> 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:

Appreciate the quick review.

> === resize property ===
> See this mail:
> https://lists.w3.org/Archives/Public/www-style/2015Mar/0051.html
> === 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).

Agreed. Deleted.

> === 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.

I appreciate the additional precision.

>> +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.

Thanks - this was quite frustrating to decipher (when checking errors
from bikeshed).

Received on Wednesday, 4 March 2015 18:01:50 UTC

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