Bug 213743 - New list tag possibilities don't match list checkbox javascript
New list tag possibilities don't match list checkbox javascript
Status: NEW
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Web Site (Show other bugs)
RHN Stable
All Linux
medium Severity medium
: ---
: ---
Assigned To: Mike McCune
Brandon Perkins
:
Depends On:
Blocks: 145467
  Show dependency treegraph
 
Reported: 2006-11-02 15:15 EST by Ken Ganong
Modified: 2008-05-01 11:39 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ken Ganong 2006-11-02 15:15:02 EST
The javascript for the check all checkbox at the top left of our tables is
located in the /javascript/check_all.js file.

There are two functions of this javascript that concerns this bug:
check_all_on_page and checkbox_clicked

The first is poorly named; it doesn't actually check all the checkboxes on the
page, it checks all of the checkboxes on the same form as the check_all checkbox.
This isn't correct though. When we have multiple lists on the same page, they
must appear in the same form, but the checkbox here should only check the ones
in the same list.

The second isn't currently rendered using the new list at all. Its purpose is to
update the check_all checkbox when another checkbox in the list is checked. So,
if you hit the check_all box and then unselect one of the others, the check_all
box becomes unselected.
This also has the same problem as the first in that it considers all the check
boxes based on being on the same form instead of being in the same list (group?)

Also, why doesn't selected a checkbox update the number checked (in the right
corners of the list)?
Comment 1 Red Hat Bugzilla 2007-04-11 21:37:43 EDT
User bnackash@redhat.com's account has been closed

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