- From: Cameron McCormack <cam@mcc.id.au>
- Date: Fri, 21 Jan 2011 09:10:27 +1300
- To: Erik Dahlstrom <ed@opera.com>
- Cc: public-svg-wg@w3.org, schepers@w3.org
Cameron McCormack: > > 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? Erik Dahlstrom: > I raised that as an issue in the old tracker some years ago: > > http://www.w3.org/Graphics/SVG/Group/track/issues/295 Ha! (exclaimed with a hint of sadness…) Do you think it is something we should change for the test suite now, or just for the future? > >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. OK. And how about for the case where it’s not a link: do you agree that the text quote above should say that text selection should start only if preventDefault() is not called? Doug: maybe you have an opinion on this, since it relates to events and default actions? -- Cameron McCormack ≝ http://mcc.id.au/
Received on Thursday, 20 January 2011 20:11:08 UTC