[ http://issues.apache.org/jira/browse/TAPESTRY-302?page=all ]
Howard M. Lewis Ship closed TAPESTRY-302:
-----------------------------------------
Fix Version: 4.0
Resolution: Fixed
I had hoped to streamline the Palette component, by moving more of the logic
into a static JS library, but just out of time. It works as advertised, and
that's what counts.
> Palette component select arrows appear enabled on load
> ------------------------------------------------------
>
> Key: TAPESTRY-302
> URL: http://issues.apache.org/jira/browse/TAPESTRY-302
> Project: Tapestry
> Type: Bug
> Components: Contrib
> Versions: 3.0.3
> Reporter: Scott Morgan
> Assignee: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 4.0
>
> When the palette component loads, both selection arrows (select/deselect)
> show the enabled images, even though they should be disabled as no items are
> highlighted on load. You can see the javascript defaulting them to disabled:
> <componentId>$buttons.selectDisabled = true;
> <componentId>$buttons.deselectDisabled = true;
> But the javascript function update_<componentId>() isn't being called, where
> the switching of the enabled/disabled images happens.
> For a workaround i've added a call to the update javascript function on page
> load. But this is semi-fragile as if the component id is changed the
> generated function name will also change.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
