[Bug 13617] New: Change wording on suspend
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13617 Bug ID: 13617 Summary: Change wording on suspend Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs@lists.koha-community.org Reporter: cbrannon@cdalibrary.org QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com I would like to suggest changing some wording on opac-user.pl. Currently the suspend button/link confuses patrons. The wording causes them to think the item is suspended. I know...it doesn't say suspended...but that doesn't seem to make a difference to the users. We would like to suggest the wording "Click to suspend", and likewise for "Click to resume". Christopher -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13617 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer@bsz-bw.de --- Comment #1 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Maybe 'suspend item' instead? I am not sure about changing the wording to have 'click' - it would also make for an awful long translation in German. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13617 paxed <pasi.kallinen@pttk.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pasi.kallinen@pttk.fi --- Comment #2 from paxed <pasi.kallinen@pttk.fi> --- (In reply to Katrin Fischer from comment #1)
Maybe 'suspend item' instead? I am not sure about changing the wording to have 'click' - it would also make for an awful long translation in German.
Also, why state something that should be obvious - if the user doesn't know it's a clickable element, something is seriously wrong with the element style. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13617 --- Comment #3 from Owen Leonard <oleonard@myacpl.org> --- (In reply to paxed from comment #2)
something is seriously wrong with the element style.
And since it is styled as a link just like any other, there shouldn't be ambiguity about its being clickable. In general I think it's not useful to tell users to click things... Especially since many of our users now use touches instead of mouse clicks. Another option is to style it as a button. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13617 --- Comment #4 from Christopher Brannon <cbrannon@cdalibrary.org> --- (In reply to Owen Leonard from comment #3)
(In reply to paxed from comment #2)
something is seriously wrong with the element style.
And since it is styled as a link just like any other, there shouldn't be ambiguity about its being clickable. In general I think it's not useful to tell users to click things... Especially since many of our users now use touches instead of mouse clicks.
Another option is to style it as a button.
IF we are concerned about touches, IMO, we should try to stay away from links and use buttons everywhere. Buttons are more touch friendly. Unfortunately, if people took the time to look things over better, I wouldn't even be reporting this. I think that is crazy that there are people trying to read books, but can't read the controls on a screen. With that said, if a button is favored over making the link a more obvious action with words, then go for it. It really does look confusing as is. Even the staff side of things makes more sense. Christopher -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13617 --- Comment #5 from Christopher Brannon <cbrannon@cdalibrary.org> --- I was able to modify the link to look like a button for the time being with jQuery, to see how that flies with patrons: //Change Suspend/Resume link to button $("#holdst td:nth-of-type(6) a,#holdst td:nth-of-type(6) button").removeClass("btn-link"); //end Change suspend link A couple odd things I notice. The class I remove is forcing it to look like a link. When I remove the class, it turns into a button! I also notice that Suspend is a an anchor tag and the Resume is a button tag. Very unusual and inconsistent. Christopher -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13617 --- Comment #6 from Owen Leonard <oleonard@myacpl.org> ---
I also notice that Suspend is a an anchor tag and the Resume is a button tag. Very unusual and inconsistent.
The suspend link is a trigger to a modal form. It could be anything--<button>, <input>, <a>... JavaScript doesn't care. If there is a consensus that it is more logical to present it as a button we can do that. The suspend link doesn't even show up if JavaScript is disabled. The resume button is an actual button which controls submission of a form. It works with and without JavaScript enabled. In both cases the element is being styled as what it is--a link and a button. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
participants (1)
-
bugzilla-daemon@bugs.koha-community.org