W3C home > Mailing lists > Public > public-html@w3.org > April 2011

Re: Bug 11239

From: Ian Hickson <ian@hixie.ch>
Date: Thu, 28 Apr 2011 18:25:06 +0000 (UTC)
To: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
cc: public-html@w3.org
Message-ID: <Pine.LNX.4.64.1104281818250.25791@ps20323.dreamhostps.com>

Just prior to seeing this e-mail I posted an updated patch to the bug:

   http://www.w3.org/Bugs/Public/attachment.cgi?id=980


On Thu, 28 Apr 2011, Benjamin Hawkes-Lewis wrote:
> > 
> > In the agreed on change proposal getCaretBlinkPeriod should return a 
> > value less than zero if no operating system setting exists. Ian 
> > removed that from the chairs decision.
> 
> Yes, I'm not sure of Ian's rationale here.

The chairs asked me to apply the bullet points here:

   http://www.w3.org/html/wg/wiki/ChangeProposals/CaretSelection#Details

...except for bullets 2 and 6. None of these bullets mention anything 
about "no operating system setting" existing. I have no idea what this 
would even mean. Is there an example of this somewhere?


> Ian: could we perhaps specify to return -1 in this case?

What case is this case, exactly? An example would be most helpful.


>   * Ian's patch is less detailed in its suggestion of how focus notification
>     should be approached, whereas your list suggests that a best fit
>     rectangle on
>     screen should be created and surfaced in the accessibility tree. I suppose
>     vagueness provides for accessibility APIs that can understand
>     non-rectangular
>     areas. Ian, could we perhaps include the best fit rectangle approach as just
>     as an example?

The best-fit approach text in the proposed patch is completely 
meaningless. I have no idea what was even _intended_ by the text. If 
someone could explain what it means, I would be happy to make sure the 
spec fully defines whatever is appropriate.


>   * Ian's patch tries to ensure notification about change of focus happens
>     after drawing the focus ring (potentially in the next event loop), whereas
>     in your list the notification happens *before* drawing the focus ring
>     (presumably preventing progress to the next event loop). Is this a bad
>     change?

It's a required change; the alternative is that every time the UA draws 
the focus ring and then the caret the magnifier would blink around 
creating exactly the kind of situation that might lead to seizures, which 
is what a big part of this patch is about avoiding.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 28 April 2011 18:25:29 UTC

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