gayatri n narlagaya...@yahoo.com writes:
If they're reading an article, might it not be better for the search
results to appear on the page with the article? There are various ways
in which you could do this, ranging from something akin to an email
client (outlook/thunderbird/etc), to google
I say whatever you do, do it consistently and the user will get it.
Even interfaces and navigational elements that break the mold do so
with a purpose; no matter how much grunge or web 2.0 is applied
to the situation.
Regarding the point about the Cancel button, I say leave it in. There
are many
On Thu, Jul 30, 2009 at 21:41, Cian OConnorcian.ocon...@gmail.com wrote:
If the situation is one in which the user has simply lost interest in
the original task, then what they'll be looking for is a route back to
whatever they were doing previously. In which case cancel is confusing
and
Thanks guys, for all the input.
Seems like there are questions regarding transaction that is going to
take place on the page.
This page is simply to read an article and when done reading be able
to go back to the results page. When I look at browser back links
they are actually icons that
At 1:28 PM -0400 7/31/09, gayatri n wrote:
This page is simply to read an article and when done reading be able
to go back to the results page.
Aha. Then it is clearly not a candidate for cancel because there is nothing
to cancel. What you want is navigational, not transactional. I'd use a
At 4:00 PM -0300 7/31/09, Gino Rodrigues wrote:
Users are rarely aware about beeing acting or navigating.
I think that's at least partly because too many designs mix up the affordances,
using one for the other.
Elizabeth
--
Elizabeth Buie
Luminanze Consulting, LLC
web: www.luminanze.com
twt:
Thanks a lot guys! The feedback is really helpful.
I initially had an informative/descriptive link to the top left of
the page, above the article title and someone said users would
confuse the Back to Results Page link to be the title of the
article. I personally didn't think so because of the
I think that a good starting point should be the difference between
primaryu and secondary actions (when talking about forms). In telling
so, I refer to the work done by Luke Wroblewski on form design. In
some cases, having a link is a good way to visually differentiate the
secondary action from
At 2:38 AM -0400 7/30/09, Pietro Desiato wrote:
I think that a good starting point should be the difference between
primaryu and secondary actions (when talking about forms). In telling
so, I refer to the work done by Luke Wroblewski on form design. In
some cases, having a link is a good way to
I skimmed this thread with interest. I agree with the proposal that if you
want a specific action to help guide the users to know it is okay (i.e.,
sometimes clicking Back breaks things and may make some folks tentative),
then having a Back to results kind of link is good. It's a familiar
Elizabeth Buie eb...@luminanze.com writes:
At 12:50 AM -0400 7/29/09, Claudia wrote:
I am of two minds on this. I have read some opinions that you don't need
a Cancel action at all (be it a button or a link), that you just need to
provide the user with clear alternatives to proceeding.
At 8:41 PM +0100 7/30/09, Cian OConnor wrote:
If the situation is one in which the user has simply lost interest in
the original task...
If the situation is one in which the user has started a transaction of
some kind, then what they really want to do is kill that transaction
to make sure it
If the current page is a later page of a multi-page form -- i.e., if the
user clicked Submit or whatever to get there (I will save my rant against
the Submit label for another time) -- then using the Back button will
often produce a dialog box asking whether or not to submit the data again.
I
Hello Everyone,
I am wondering if using buttons or navigational elements that look
like buttons(for e.g BACK link) are intuitive?
Let me give you guys some context here:
I am working on designing a knowledge base interface where a user can
look for articles and click on a particular link to
From my experience, a button is usually significant in a moving
forward submitting ... as in dong something.
However, I have encountered imballances in my design work which
required a sort of hybrid. For a user to easily navigate and move
forward without having to think much on it, usually it'll
Based on convention I would say that hyperlinks indicate navigation,
buttons indicate actions. To differentiate navigating from acting:
navigating doesn't change any data, is reversible; acting does
change data or is not reversible. I would put Back and Cancel under
navigating, and Submit, Save,
Hi,
I also know the problem particularly when I discuss with developers.
Often I have the situation that we have a form that can be submitted
(so we have a save or ok button) and we have a cancel
button.
The points we discuss is:
- do we need a cancel button on a website where you can click
Hi
If you see gmail interface, they have a 'Back to Inbox' text link
unlike its adjacent buttons. This is to make the back more prominent
for the user and also that it is in blue underlined (a convention for
links).
You can use the button if that is the only button in that row or
column, or you
GN,
My general rule of thumb for links vs. buttons is this: links take
you places, buttons perform an action. However, in form submission or
a wizard-like submission process (especially in applications), I've
found that users expect to see buttons to continue, cancel, edit or
go back in the
of
Buttons versus Links for Navigation
07/29/09 10:55 AM
At 12:50 AM -0400 7/29/09, Claudia wrote:
I also know the problem particularly when I discuss with developers.
Often I have the situation that we have a form that can be submitted
(so we have a save or ok button) and we have a cancel
button.
The points we discuss is:
- do we need a cancel button
My initial response would be - surely the users can just use the back
button? Unless there's specific reasons you've identified why this
won't work for your project of course.
Assuming you do need an element on the page that takes the users
back, then I would agree with the others here that you
Have you considered calling the link 'Return to search results' if
they've arrived via site search results? Do you really need a back
link / button for other situations? What if they've arrived via
search engine?
I'd let the browser Back button take priority here, apart from if
they've come via
23 matches
Mail list logo
