Double Click wagn.org Text

Support Ticket

+status
answered
 

If one double clicks any page on wagn.org, the site displays the following :

 

Ooo. Sorry, but...

You have to sign in to update this card: Introduction.

If you click the non-link text below the lackluster video at http://wagn.org/introduction, it displays the sorrow.

 

Thanks! We intend to add setting for edit controls which will make it possible to turn off double-click-to-edit.  Since we'll still want people to have a way to edit content, we also are working to make simple edit-alternative to double click.

 

But on any Wagn that has double-click-to-edit turned on, if you double-click on something that you have to be signed in to edit there has to be something like what you're seeing here. Does that make sense? I think we've talked about improving it, but I'm not seeing a ticket for it. If you have any ideas about how to improve this, we'd love to hear it... --John Abbe


I think the key problem here is that new/casual users have no way of knowing that double clicks are supposed to trigger edits. Unless I'm misunderstanding, that's what this support ticket is about -- someone double clicked expecting to highlight text and found this result confusing.

 

If you know that double-clicking triggers edits, the message makes decent sense. Perhaps we should add more info to the message for non logged in users?

 

Fwiw, you can actually turn off all double clicking with an (intentionally undocumented so far) "*double click" card (make it a toggle). But I'm wondering if we don't need more nuance. And, ultimately, whether this shouldn't be a user preference.

  --Ethan McCutchen.....2013-03-04 18:31:52 +0000


I agree that it should be a user preference ultimately. Maybe we should start a ticket to collect things like this - implement user preferences?

 

In any case we could obviously also improve error message when trying to edit cards requiring signin. This would be relevant when going to an edit URL when not signed in as well, Although given the nature of the confusion maybe we need different error messages for those two situations?

  --John Abbe.....2013-03-04 18:58:49 +0000


we do have this: add persistent user preferences and GUI for them. I haven't checked in there in a while...

  --Ethan McCutchen.....2013-03-04 19:35:01 +0000


you could also make the case for just turning off double-click-to-edit for anyone not signed in (always). probably decent default behavior...

  --Ethan McCutchen.....2013-03-04 19:37:22 +0000


I think that makes sense - shall I ticket it?

 

In any case, if an admin does want it on, and of course when we get around to the user preferences, an improved error message seems worthwhile, so shall I ticket that as well?

  --John Abbe.....2013-03-10 02:52:47 +0000