I agree that if we tell the user what's going to happen, it's a better
user experience.
That said, most users won't read any text at all, and just start
typing, so I'm thinking that maybe we're better off explaining *after*
rather then before.
"Before you continue, please make sure your bug hasn't been reported:"
I agree that if we tell the user what's going to happen, it's a better
user experience.
That said, most users won't read any text at all, and just start
typing, so I'm thinking that maybe we're better off explaining *after*
rather then before.
"Before you continue, please make sure your bug hasn't been reported:"
We have some preliminary mockups of an ajaxy version of reporting bugs: /wiki.canonical .com/Launchpad/ UI/Bugs/ ThreeDotO? action= AttachFile& do=view& target= report_ bug_start. jpg /wiki.canonical .com/Launchpad/ UI/Bugs/ ThreeDotO? action= AttachFile& do=view& target= dupe_checker. jpg
https:/
and
https:/
--
Martin