Bug 979 - [Chameleon] Buttonizer buttons - load in their default state, then become active
: [Chameleon] Buttonizer buttons - load in their default state, then become active
Status: RESOLVED FIXED
: Chameleon
Widget
: 2.2
: PC Windows 2000
: P3 enhancement
: FUTURE
Assigned To:
:
:
:
:
:
  Show dependency treegraph
 
Reported: 2005-03-01 13:11 by
Modified: 2005-06-06 14:38 (History)


Attachments


Note

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


Description From 2005-03-01 13:11:42
Right now, an application that uses buttonizer and the multi-state buttons will
load up the page with all the buttons in their default state, and then the
onLoad event will change "active" buttons to their clicked in image.

Would it be possible to have the page load with the buttons already "clicked"
instead of having them load and then become clicked?

This is a minor thing, but it contributes to the jarring effect of the page reload.
------- Comment #1 From 2005-05-27 09:47:26 -------
I think it's a small thing setting to 2.2.
------- Comment #2 From 2005-06-06 14:38:23 -------
This was a small fix. Instead of drawing the image with the 'normal' image, it
is drawn with the 'selected' one when it's the current button. However, if
multiple buttons have the default state, multiple button wil be clicked and then
the non-default will be unclicked.

This is probably good for the developper to be able to detect the problem in the
template.

Marking as FIXED.