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

Re: [1.2T-LC] Text selection - but what about Find Text? (ISSUE-2065)

From: Doug Schepers <schepers@w3.org>
Date: Mon, 22 Sep 2008 01:06:12 -0400
Message-ID: <48D727C4.8000002@w3.org>
To: Jeff Schiller <codedread@gmail.com>, www-svg <www-svg@w3.org>

Hi, Jeff-

Thanks for your comment.

Jeff Schiller wrote (on 9/21/08 10:58 PM):
> I notice that text selection and clipboard operations are still
> recommended by the SVG spec [1], but I would consider it useful if SVG
> Viewers that support "Find Text" operations also supported "Find Text"
> in SVG <text> and <textArea> elements.  Additionally, some suggested
> behavior that SVG Viewers should follow in the case of text fragment
> being found would be useful to improve interoperability across
> implementations (pan and zoom to text?).

I agree with you about this, and we probably should clarify the spec in
this regard.

In fact, I reported this as a bug on Mozilla [1], and I even started to
patch it before XPCOM made me run away like a frightened child.  There
was also a duplicate [2] of my bug, with a link to a diagram [3] that
illustrates the use case.  I also have a sample that shows how it might
work as embedded content. [4]

Right now, Opera doesn't find the text at all; Firefox may or may not,
but doesn't pan to it when you search, and doesn't highlight the string;
and Safari does find the strings and gives you a count of them, but
doesn't pan to show them, or highlight the string (though it does work
somewhat when the SVG is embedded in HTML, see my example... as it
stands, while it still needs improvement, I have to give highest props
to WebKit).  This is definitely a point on which ambiguity in the spec
has led to a lack of interoperability that harms the user (and author)
experience.

That said, it is also a UI feature, which some folks believe shouldn't
be specified.  If we were to put it into the spec at this point, it
would probably be in the conformance or text sections, and would be a
recommendation (that is, not normative) to behave similarly to the
fragment-id behavior. [5]  We could test the waters, and strengthen the
wording in SVG Core 2.0, perhaps.

I have raised this as an issue, and the SVG WG will discuss it and get
back to you promptly.


[1] https://bugzilla.mozilla.org/show_bug.cgi?id=330045
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=450621
[3]
http://upload.wikimedia.org/wikipedia/commons/7/74/Timeline_of_web_browsers.svg
[4] http://svg-whiz.com/svg/w3c/textSelection.html
[5] http://www.w3.org/TR/SVGMobile12/linking.html#SVGFragmentIdentifiers


Regards-
-Doug Schepers
W3C Team Contact, SVG and WebApps WGs
Received on Monday, 22 September 2008 05:06:50 GMT

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