Re: [whatwg] On accessibility

On Thu, 15 Jun 2006 09:42:41 +0700, Matthew Paul Thomas <[EMAIL PROTECTED]> wrote: >> What Opera does makes sense. Maybe it should be standardized. > What Opera does is indeed very cool, but it's quite possible that > another browser could come up with something even cooler. And in this > area t

Re: [whatwg] On accessibility

Alexey Feldgendler wrote: On Thu, 15 Jun 2006 08:09:43 +0700, Lachlan Hunt <[EMAIL PROTECTED]> wrote: Accesskey implementations need to be seriously improved if they are to be retained. There's significant evidence to show that there are very few, if any, safe keys available which don't clas

Re: [whatwg] On accessibility

On Jun 14, 2006, at 9:47 PM, Alexey Feldgendler wrote: On Thu, 15 Jun 2006 08:09:43 +0700, Lachlan Hunt <[EMAIL PROTECTED]> wrote: Accesskey implementations need to be seriously improved if they are to be retained. There's significant evidence to show that there are very few, if any, safe

Re: [whatwg] On accessibility

On Thu, 15 Jun 2006 08:09:43 +0700, Lachlan Hunt <[EMAIL PROTECTED]> wrote: Accesskey implementations need to be seriously improved if they are to be retained. There's significant evidence to show that there are very few, if any, safe keys available which don't clash with existing shortc

Re: [whatwg] On accessibility

Simon Pieters wrote: I've spoken to a person who is blind about HTML5 and accessibility. I thought I'd send some of his thoughts to the list. ... He also says that he accesskeys shouldn't be dropped. Accesskey implementations need to be seriously improved if they are to be retained. There's

[whatwg] On accessibility

Hi, I've spoken to a person who is blind about HTML5 and accessibility. I thought I'd send some of his thoughts to the list. He is in favor of the new and elements indicating the navigation section of the page and what is the main content: yeah that'd be excellent, if screen readers woul

[whatwg] CDATA - white space handling for param element values

CDATA - white space handling for param element values The current CDATA spec is: 1. Replace character entities with characters, 2. Ignore line feeds, 3. Replace each carriage return or t

Re: [whatwg] Mathematics in HTML5

Oistein E. Andersen wrote: > > This issue [font selection] belong to presentational layer and has to be > > addressed > >on CSS side (there are no problems on XSL and/or DSSSL side as one can make > >appropriate transformations). > > I am not so sure about that. In fact I am not sure either.

Re: [whatwg] Mathematics in HTML5

Oistein E. Andersen wrote: > As a first step, I have tried to transform the TeX code used on > Wikipedia (http://en.wikipedia.org/wiki/Help:Formula) into HTML5. > This raises some issues, see http://xn--istein-9xa.com/HTML5/WikiTeX.pdf for > all the details. I have tried to follow the current pro

Re: [whatwg] [html5] HTMLMapElement.images

Anne van Kesteren wrote: Basically finding the position of the associated image elements so that you can show "popups" and so more easily without hardcoding that a particular image belongs to that map and vice versa. https://bugzilla.mozilla.org/attachment.cgi?id=67731&action=view ... has a

Re: [whatwg] [html5] HTMLMapElement.images

Quoting Shadow2531 <[EMAIL PROTECTED]>: On 6/13/06, Anne van Kesteren <[EMAIL PROTECTED]> wrote: Before I forget about this hereby a proposal to give the HTMLMapElement interface a new (readonly) member called `images` or equivalent representing an HTMLCollection consisting of HTMLImageElement a

Re: [whatwg] [html5] HTMLMapElement.images

Quoting Ian Hickson <[EMAIL PROTECTED]>: On 6/13/06, Anne van Kesteren <[EMAIL PROTECTED]> wrote: Before I forget about this hereby a proposal to give the HTMLMapElement interface a new (readonly) member called `images` or equivalent representing an HTMLCollection consisting of HTMLImageElement