Security

(public)

User Story

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
http://www.peepo.com/svg/keycode.svg
SVG on osX using asv3 works in safari but not mozilla or firefox
use the keyboard to type a letter, teh keycode is displayed on screen, well it
should be and is in safari.
essential for many games
Reproducible: Always
Steps to Reproduce:
1.
2.http://www.peepo.com/svg/keycode.svg
3.type a letter using a keyboard
Actual Results:
nothing
Expected Results:
screen should display keycode for letter typed
this code works in safari, and msie

This is also broken for win'98 and asv3
SVG is scaleable vector graphics an open source graphics format that is saved
in plain text,and provides an interface roughly similar to flash but with
additional accessibility functionality.
asv3 is a plugin from adobe: http://www.adobe.com/svg/viewer/install/main.html
please note this is unlikely to be a plugin issue as safari is not broken with
the identical plugin

well I'm fairly miserable that 5 months later this bug hasn't been assigned.
accessibility doesn't seem to have a very high priority here :-(
on the positive side Aaron wrote me suggesting this is a plugin issue, so I
tightened the code up slightly, (removed references to adobe) and tested with
the latest MozSVG build for mac:
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040702
It doesn't work :-(
keyboard users, such as people with low vision, etc are being let down, and I
believe the whole open source community, including gnome, by this essential
accessibility functionality for SVG.
so have raised theseverity, to critical, until assigned

http://www.w3.org/TR/SVG11/interact.html#SVGEvents
"As in DOM2 Key events, the SVG specification does not provide a key event set.
An event set designed for use with keyboard input devices will be included in a
later version of the DOM and SVG specifications."
There are now Text events and Keyboard events we could support as described in
the W3C Note DOM Level 3 Events at
* http://w3.org/TR/DOM-Level-3-Events/events.html#Events-KeyboardEvents-Interfaces
* http://w3.org/TR/DOM-Level-3-Events/events.html#Events-TextEvents-Interfaces
but currently the only feature in the SVG 1.2 draft (which we don't support BTW)
that would allow you to use them would be the <handler> element
(http://www.w3.org/TR/SVG12/#xmlevents-integration). There are no event handler
attributes such as onkeypress or ontext described, and I don't imagine that
these will be added to SVG 1.2. Currently Mozilla's native SVG implementation
only supports the following event attributes.
* onclick
* onmousedown
* onmouseup
* onmouseover
* onmousemove
* onmouseout
* onload
That's not necessarily to say that won't support key events and key event
attributes in the future, but please file a *separate* bug request for support
of these in Mozilla's native SVG implementation. Fixing it for the native
implementation is a very separate issue to fixing it for Adobe's plugin.

jwatt,
I asked the DOMWG regarding this and received this response from Joseph Kesselman:
Certainly the accessability working group could, and probably should,
address this. But I think "keyboard navigation" is out of scope for the
DOM.
Remember, the DOM is a Document Model API. Screen navigation is an user
interface issue. The DOM will happily pass those characters through its
event system. But how they're interpreted by the UI is not under the DOM's
control, so there isn't anything the DOM spec can usefully say about this.
http://lists.w3.org/Archives/Public/www-dom/2004OctDec/0005.html

This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/