- From: Erik Dahlstrom <ed@opera.com>
- Date: Thu, 20 Jan 2011 13:58:12 +0100
- To: public-svg-wg@w3.org
On Thu, 20 Jan 2011 04:51:26 +0100, Cameron McCormack <cam@mcc.id.au> wrote: > text-tselect-01-b asserts that text selection shouldn’t span multiple > <text> elements: > > http://dev.w3.org/SVG/profiles/1.1F2/test/harness/htmlObjectMini/text-tselect-01-b.html > > Safari allows text selection across <text> elements. This doesn’t seem > like such a bad thing. Are we sure we want this not to be allowed? I raised that as an issue in the old tracker some years ago: http://www.w3.org/Graphics/SVG/Group/track/issues/295 > Relatedly, I see this in text.html#TextSelection: > > A text selection operation starts when all of the following occur: > … > * no links or events have been assigned to the ‘text’, ‘tspan’ or > ‘textPath’ element(s) (or their ancestors) associated with the > given glyph. > > Shouldn’t this be if the events handlers don’t call preventDefault()? IMO selecting text that is a link should always be allowed, without any changes to content and without requiring a script to run. /Erik -- Erik Dahlstrom, Core Technology Developer, Opera Software Co-Chair, W3C SVG Working Group Personal blog: http://my.opera.com/macdev_ed
Received on Thursday, 20 January 2011 12:58:53 UTC