Bug 81279 - "Update" and "Apply Errata" buttons easily confused
Summary: "Update" and "Apply Errata" buttons easily confused
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Network
Classification: Retired
Component: RHN/Web Site
Version: RHN Stable
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mike Orazi
QA Contact: Red Hat Satellite QA List
URL: https://rhn.redhat.com/network/system...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-01-07 15:13 UTC by Fred Bacon
Modified: 2008-02-12 17:45 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-02-12 17:45:03 UTC
Embargoed:


Attachments (Terms of Use)

Description Fred Bacon 2003-01-07 15:13:51 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
When checking the errata for a system, two buttons appear on the left hand side.
 One says "Update" the other says "Select All".  On the right hand side is a
button saying "Apply Errata".  Since a user is attempting
to update their system, the natural behavior would be for them to click on the
"Update" button to complete the action.  This is particularly true for cultures
where reading is from left to right.  You see the "Update" button long before
you see the "Apply Errata" button.  I believe that the button currently labeled
"Update" would be more appropriately labeled as "Refresh", since this is the
intended behavior.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Go to list of systems.
2.Select a system with errata available.
3.Click on the Errata tab.
    

Additional info:

Comment 1 Bill C. Riemers 2008-02-12 17:45:03 UTC
I see the button name has been changed to "Update List" instead of just
"Update".  I agree that "Refresh" would be more meaningful for this particular
page, but it would be confusing because all other RHN pages use "Update List" as
well.



Note You need to log in before you can comment on or make changes to this bug.