W3C home > Mailing lists > Public > www-svg@w3.org > March 2008

Re: SVGt1.2: Text Box

From: Andreas Neumann <a.neumann@carto.net>
Date: Mon, 17 Mar 2008 14:59:37 +0100 (CET)
Message-ID: <41033.193.246.86.39.1205762377.squirrel@webmail.customers.iirc.at>
To: j.chetwynd@btinternet.com
Cc: "www-svg List" <www-svg@w3.org>

Hi Jonathan,

> It does not seem to me to be acceptable to release SVGt1.2 when the
> only means to enter text relies on javascript.
> Most especially given the difficulty in changing matters after a spec
> is released.

A later potential SVG-App or SVG-GUI module would not contradict with the
spec and it wouldn't have to change the existing SVG 1.2 Tiny spec. It
would be an add-on/extension. The current focus of the SVG WG is to
release the SVG 1.2T spec and not making lots of add-ons and never finish
the spec. There can always be a later, improved version.

> Supposedly improved ease of implementation is a consideration,
> however the benefits are limited, if the process produces resources
> that are not readily accessible and re-purposable.

Again - SVG can and should be used in conjunction with HTML. It is not
meant as a replacement or duplication of all of HTMLs features. If
something can be accomplished relatively easy in HTML - why not use HTML?

>
> Please would you consider updating your textbox example?
> It does not appear to be keyboard navigable.

I don't claim that my code is perfect. You may use it and improve it. My
textbox example obviously has some deficiencies, but it still might be one
of the most complete SVG textbox examples available.

> no title is provided, according to the specification every standalone
> document should have a title.

yes, will fix it

> the script you provide is relatively long, most especially when
> compared with the ease of use of html textbox.

This is true. Of all SVG widgets I made, the textbox is the most difficult
and complex one. Also, due to different behavior of UAs where one has to
find workarounds. As an example, not UA behave the same with evt.keyCode
and evt.charCode.

> you'll appreciate that this makes it unlikely that others will follow
> your lead.

ok - but what can I do about it? Either one sacrificies flexibility or one
sacrificies ease of use for developers.

> similarly if others do use your code it is important that it is fully
> accessible.

It certainly can improve. And will be improved over time.

> Having said which I am particularly encouraged by your inclusion of
> caret, backspace and string.length features, and will endeavour to
> include them.

good - you will quickly find out that UAs don't behave consistently, also
due to the fact that keyboard handling never was standardized. This is the
same issue in HTML btw.

Andreas

-- 
Andreas Neumann
Böschacherstrasse 6, CH-8624 Grüt/Gossau, Switzerland
Email: a.neumann@carto.net, Web:
* http://www.carto.net/ (Carto and SVG resources)
* http://www.carto.net/neumann/ (personal page)
* http://www.svgopen.org/ (SVG Open Conference)
* http://www.geofoto.ch/ (Georeferenced Photos of Switzerland)
Received on Monday, 17 March 2008 14:00:28 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:38 GMT