[
https://issues.apache.org/jira/browse/TAP5-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17897829#comment-17897829
]
Ben Weidig commented on TAP5-2790:
----------------------------------
I could recreate the issue in a Selenium test but I didn't get your solution to
work when I tried to adapt it to the underlying CoffeeScript.
Maybe it's a better idea to redo the whole script (TypeScript?) and store a
mapping for which option belongs to which group, if any, so moving them back
and forth is easier.
> Palette with option groups within the SelectModel does not work properly.
> -------------------------------------------------------------------------
>
> Key: TAP5-2790
> URL: https://issues.apache.org/jira/browse/TAP5-2790
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.9.0, 5.8.7
> Reporter: LRein
> Assignee: Ben Weidig
> Priority: Trivial
> Labels: easyfix
> Attachments: palette.js
>
>
> Option Groups are displayed correctly in the Palette. If you select options
> and then deselect them again, they are not placed in the correct option group.
> I am currently correcting the behavior of the Palette when overwriting the
> palette.js. But it would be much better if you could adopt the corrected
> behavior.
> {code:java}
> @Contribute(ModuleManager.class)
> public static void overrideTapestryCoreModules(
> MappedConfiguration<String, Object> configuration,
> @Path("META-INF/assets/js/override/palette.js") Resource palette)
> {
> configuration.add("t5/core/palette", new
> JavaScriptModuleConfiguration(palette));
> } {code}
>
> In Attachments is the change that corrects the behavior of the palette.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
