Re: text selection test

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:

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 ≝

Received on Thursday, 20 January 2011 20:11:08 UTC