Disabled/Enabled RW - events propagation - questions
by Juraj Húska
Hello guys, again me.
I am testing +disabled+ option of the +pickList.+
When I set this option to +true+, than it is disabled as expected (disabled classes are rendered - user can not interact with it).
However, when I am trying to interact with that +pickList+ with JQuery, than it state is changed - I guess this is *expected*, as there is no way to avoid it, we can only disable the functionality which is achieved in standard way. Right ?
*But,* what is kind of interesting is that *change event* is triggered even when working with such disabled +pickList+. Is this correct ? IMHO we can check before triggering of such event whether the RW is enabled. The question is whether it is needed ? I think it applies to all RWs.
Cheers
Juro
Posted by forums
Original post: https://community.jboss.org/message/844601#844601
11 years, 2 months
Change in resource packaging
by Michal Petrov
Hi all,
we needed to split Core and UI packed resources for RF 5 to work with RF 4.5 (RF-13280 (https://issues.jboss.org/browse/RF-13280)). To achieve this I have changed the pack parameter of the resource plugin to accept a string (filename) instead of a boolean.
This should not cause any issues with current configurations since users should not be referencing the packed files directly (they will only end up being named true.js/true.css instead of packed.js/…). It will however cause an issue where packing is explicitly disabled (i.e. <pack>false</pack>). The old parameter defaulted to false so there was no reason for doing this but I noticed we were doing in RF 4 anyway. Are we expecting this to be a significant case?
Michal
Posted by forums
Original post: https://community.jboss.org/message/844299#844299
11 years, 2 months
