On Mon, Mar 31, 2014 at 8:16 PM, Cameron McCormack <cam@mcc.id.au> wrote: > Rik Cabanier: > > Should it be optional in the IDL for SVGElement then? > > It's an IDL attribute, not an argument to an IDL operation, so optional > doesn't really make sense. Do you mean nullable, where null would > indicate that the content attribute is missing? Yes, that is what I meant > If so, then no, I think > we should just behave the same as HTMLElement.tabIndex (and other SVG > attributes where we reflect content attributes that have lacuna values) > and have it be 0 or -1. A difference with the HTML spec is that tabIndex is allowed on any element. Setting a tabindex of 0 on a <rect> for instance, will make it focusable. See https://svgwg.org/svg2-draft/interact.html#sequential-focus-navigation-and-the-tabindex-attribute
Received on Tuesday, 1 April 2014 03:42:43 UTC