[whatwg] hit regions: limited set of elements for fallback content
ian at hixie.ch
Thu Feb 20 11:43:38 PST 2014
On Thu, 20 Feb 2014, Dominic Mazzoni wrote:
> On Thu, Feb 20, 2014 at 10:37 AM, Ian Hickson <ian at hixie.ch> wrote:
> > So far, it seems like to support grids in canvas, we need:
> > - enable table-related elements (table, td, tfoot, etc) to be hit region
> > controls. (exclude col and colgroup)
Filed this as: https://www.w3.org/Bugs/Public/show_bug.cgi?id=24750
> > - fire an event on an element when the user agent (possibly because of a
> > request from the AT, but not necessarily) wants to scroll to an
> > element; default action is to actually scroll.
> > - when this event is fired on a canvas, include the region information.
Filed this as: https://www.w3.org/Bugs/Public/show_bug.cgi?id=24748
> > ...and to support list boxes, we need:
> > - enable <select multiple> elements to be hit region controls.
> > - enable <select size=N> eements where N>1 to be hit region controls.
> > - enable <option> to be hit region controls.
> > - optionally, if implementors are on board:
> > - make <select size=1> in <canvas> act like size=N where N>1.
> > - enable <select size=1> elements to be hit region controls.
Filed this as: https://www.w3.org/Bugs/Public/show_bug.cgi?id=24749
> > What's your take on the <select> thing; should we have a special case
> > in browsers for size=1, or should we require size>1?
> I can't think of a way to make size=1 work, so requiring size>1 may be
> the only option. It seems ugly, though.
The way we could make it work would be to change the logic in the <select>
so that when it's in a canvas, it's a list box and not a drop-down. But
that might be more confusing than requiring that people set size=2? I
guess I'll just punt on this for now and we'll see whether authors get
confused or not.
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
More information about the whatwg