W3C home > Mailing lists > Public > public-html@w3.org > February 2012

Re: Split Issue 30?

From: Jonas Sicking <jonas@sicking.cc>
Date: Sun, 12 Feb 2012 23:23:44 -0500
Message-ID: <CA+c2ei8_UCTRB7NM8HYC2WsTpFKuyo4XarPsa3U6qqk0H9ymfQ@mail.gmail.com>
To: Charles Pritchard <chuck@jumis.com>
Cc: Maciej Stachowiak <mjs@apple.com>, Laura Carlson <laura.lee.carlson@gmail.com>, Sam Ruby <rubys@intertwingly.net>, public-html@w3.org
On Sun, Feb 12, 2012 at 10:16 PM, Charles Pritchard <chuck@jumis.com> wrote:
> On 2/12/2012 6:48 PM, Jonas Sicking wrote:
>>
>> On Sun, Feb 12, 2012 at 7:19 PM, Charles Pritchard<chuck@jumis.com>
>>  wrote:
>>>
>>> On 2/12/2012 3:42 PM, Jonas Sicking wrote:
>>>>>>
>>>>>>  Jonas, you have a different perspective too. That's OK, too. Multiple
>>>>>>  viewpoints are a good thing. We are fleshing out real issues in this
>>>>>>  process.
>>>>
>>>> It sounds like your only objection to allowing aria-describedby to
>>>> point to @hidden elements is that it will delay publishing a finalized
>>>> HTML5 spec. That is certainly an understandable argument, though given
>>>> the extreme inertia for changing semantics of existing features, I'd
>>>> rather spec the @hidden attribute correction from the beginning, than
>>>> wait to fix it in HTML6.
>>>
>>>
>>> My comment was intended as: we should wait to break current behavior,
>>> until
>>> HTML6. If you want to consider it like breaking a bone to reset it,
>>> that's
>>> the idea.
>>> The current situation of position, visibility: hidden and display: none
>>> is
>>> well tested, and I am certainly being conservative in my position of
>>> altering core CSS architecture.
>>>
>>> As I understand it, @hidden is a shortcut for display: none, in
>>> implementation and markup and may be implemented through the css
>>> selector:
>>> [hidden] { display: none; }.
>>>
>>> I'm concerned about the structural problems of altering the CSSOM
>>> behavior
>>> display: none.
>>
>> No one is suggesting to change how CSSOM or display:none works. Please
>> see my change proposal, it does none of these things.
>>
>> It sounds to me like you are worried about various changes to the
>> internals of browsers. So far none of the actual browser implementors
>> have expressed this concern. In fact, both Maciej and I have said that
>> this seems implementable and that we have to write similar code anyway
>> to support<canvas>  accessibility.
>>
>> I'd have a lot more understanding for you being concerned if you
>> actually were implementing a browser. I much rather that we ask people
>> who actually implement browsers what is implementable.
>
>
> I've implemented and produced implementations of significant chunks of CSSOM
> and HTML Forms in Canvas, as well as implementing the various prerequisites
> needed for those implementations to work on a variety of existing graphics
> APIs.
> webkit uses display: none for @hidden.

As I've already stated, the CSSOM and other specifications you are
talking about is irrelevant to the subject matter, which is ISSUE 30,
i.e. how various content is exposed to AT.

It appears we simply do not agree on how a number of issues (probably
including which issues we don't agree on :-) ) so I suspect this
thread won't go any further.

/ Jonas
Received on Monday, 13 February 2012 04:24:41 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:30 UTC