[JBoss JIRA] (RF-11180) select: selecting from unorder list selects the wrong item
by J W (JIRA)
[ https://issues.jboss.org/browse/RF-11180?page=com.atlassian.jira.plugin.s... ]
J W commented on RF-11180:
--------------------------
there is a workarround for this issue already. check: https://issues.jboss.org/browse/RF-12613
> select: selecting from unorder list selects the wrong item
> ----------------------------------------------------------
>
> Key: RF-11180
> URL: https://issues.jboss.org/browse/RF-11180
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: base functionality, component-selects
> Affects Versions: 4.0.0.Final
> Environment: Win7_64 + Firefox 5, Chrome 11 andIE9
> Reporter: Yonatan Graber
> Assignee: Brian Leathem
> Labels: rich:select, select
> Fix For: 5-Tracking
>
>
> If rich:select relays on an items list which includes two items, one is a a prefix of the other, and the shorter one should be placed before the longer one in the list, you can't pick the shorter one (if manual input is enabled).
> You should look at reproduction steps for an example, which is much more clearer than the general description of the issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (RF-13033) inputNumberSlider, inputNumberSpinner: @label is not working
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RF-13033?page=com.atlassian.jira.plugin.s... ]
Jiří Štefek commented on RF-13033:
----------------------------------
Well the VDL-DOC is only saying 'A localized user presentable name for this component', but doesn't mention where it is used. So, [~bleathem], can you, please, give me a simple example?
> inputNumberSlider, inputNumberSpinner: @label is not working
> ------------------------------------------------------------
>
> Key: RF-13033
> URL: https://issues.jboss.org/browse/RF-13033
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input, doc
> Affects Versions: 3.3.2.CR1, 4.3.2, 5.0.0.Alpha1
> Reporter: Jiří Štefek
> Assignee: Jiří Štefek
> Fix For: 4.3.4
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> These two components have attribute @label.
> And it doesn't work -- there is no sign of it on the page source.
> Where should it be displayed? Should it replace the default value?
> Or should this attribute be deleted?
> Please also update the VDL-DOC in all cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (RF-11275) showcase - rich:popup - Sample Modal panel - after changing the size of popup there is double shadow
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-11275?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-11275:
-------------------------------
Original Estimate: 1 hour
Remaining Estimate: 1 hour
> showcase - rich:popup - Sample Modal panel - after changing the size of popup there is double shadow
> ----------------------------------------------------------------------------------------------------
>
> Key: RF-11275
> URL: https://issues.jboss.org/browse/RF-11275
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: showcase
> Affects Versions: 4.1.0.Milestone2
> Environment: richfaces-showcase-4.1.0.20110805-M1-jee6.war
> container - JBoss AS 6.0.0.Final
> browser - Chrome 13, IE 9, FF 3.6
> Reporter: Juraj Húska
> Fix For: 4.3.4
>
> Attachments: popupShadowWrong.png
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> When I call the popup first, everything is OK. But when I change the size of popup panel, next invoked popup has double shadow at some particular part of the page. Please see the attachment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (RF-13095) extendedDataTable tableState setter not called on column resize/reorder
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13095?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13095:
-------------------------------
Original Estimate: 1 hour
Remaining Estimate: 1 hour
> extendedDataTable tableState setter not called on column resize/reorder
> -----------------------------------------------------------------------
>
> Key: RF-13095
> URL: https://issues.jboss.org/browse/RF-13095
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.2
> Environment: GlassFish 3.1.2.2 with Mojarra 2.1.23, tested on Firefox 22 and Chrome 28.
> Reporter: Salvo Isaja
> Fix For: 4.3.4
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> Not sure if this qualifies as a bug or a feature request.
> I have an extendedDataTable with the tableState attribute bound to a String property of a backing bean (tried both a request scoped bean on a transient view and a session scoped bean on a stateful view).
> When resizing or reordering columns, an Ajax request is posted to the server, and I correctly see the new column layouts in the request, but the setter of the tableState property in the backing bean is not called. If I execute @form on a a4j:commandLink or commandButton, it is called instead.
> Thanks
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (RF-12989) Documentation for togglePanelItem is wrong and 4.2.2 components are not working anymore in 4.3.0.Final
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12989?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-12989:
------------------------------------
Having looked at the [relevant commit|https://github.com/richfaces4/components/commit/e6939c36ffc56661df...], I can see that prior to RF 4.3.0, the name would default to the component id, whereas after RF 4.3.0, the name defaults to the clientId.
So it *should* still be possible to not use a name, and only use an id, but any further checks/manipulations would have to use the clientId, rather than the id.
When you say "the page does not work anymore", what do you mean? What functionality breaks?
> Documentation for togglePanelItem is wrong and 4.2.2 components are not working anymore in 4.3.0.Final
> ------------------------------------------------------------------------------------------------------
>
> Key: RF-12989
> URL: https://issues.jboss.org/browse/RF-12989
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: doc
> Affects Versions: 4.3.0.Final
> Environment: JBossAS 7.1.1
> Reporter: Andrea Martino
> Assignee: Brian Leathem
> Priority: Minor
> Labels: togglePanel
> Fix For: 4.3.4
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> In RichFaces 4.2.2 it was possible to define togglePane items using id as attribute, as following {code}<rich:togglePanelItem id="item1">{code}
> With RichFaces 4.3.0 the page does not work anymore, I had to change the attribute to name {code}<rich:togglePanelItem name="item1">{code}
> The docs still say id is valid, even when it's not [http://docs.jboss.org/richfaces/latest_4_3_X/Component_Reference/en-US/ht...]. Either the docs should be changed or id attribute should be accepted as it was before.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (RF-13033) inputNumberSlider, inputNumberSpinner: @label is not working
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13033?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-13033:
----------------------------------
Assignee: Jiří Štefek (was: Brian Leathem)
[~jstefek] the _@label_ attribute is used by validators when displaying messages. Is that the use case you are looking for when you say "it does not work"?
> inputNumberSlider, inputNumberSpinner: @label is not working
> ------------------------------------------------------------
>
> Key: RF-13033
> URL: https://issues.jboss.org/browse/RF-13033
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input, doc
> Affects Versions: 3.3.2.CR1, 4.3.2, 5.0.0.Alpha1
> Reporter: Jiří Štefek
> Assignee: Jiří Štefek
> Fix For: 4.3.4
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> These two components have attribute @label.
> And it doesn't work -- there is no sign of it on the page source.
> Where should it be displayed? Should it replace the default value?
> Or should this attribute be deleted?
> Please also update the VDL-DOC in all cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (RF-13117) ExtendedDataTable Sorting resets $(window).resize Events
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13117?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-13117.
--------------------------------
Resolution: Done
> ExtendedDataTable Sorting resets $(window).resize Events
> --------------------------------------------------------
>
> Key: RF-13117
> URL: https://issues.jboss.org/browse/RF-13117
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.3
> Environment: Tomcat 7
> JBoss 7.1
> Reporter: Thomas Zuberbuehler
> Assignee: Brian Leathem
> Labels: regression
> Fix For: 4.3.4
>
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> Sorting removes other resize events.
> At some point following code is called:
> {code}
> // extendedDataTable.js
> deActivateResizeListener: function() {
> $(window).off(this.resizeEventName);
> }
> {code}
> Notice that this.resizeEventName is undefined.
> Before code is invoked (Chrome JavaScript console)
> {code}
> $._data(window,'events').resize
> [Object, Object]
> {code}
> After invoking
> {code}
> $._data(window,'events').resize
> TypeError: Cannot read property 'resize' of undefined
> {code}
> http://stackoverflow.com/questions/18045891/how-to-check-if-onresize-meth...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (RF-13117) ExtendedDataTable Sorting resets $(window).resize Events
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13117?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13117:
------------------------------------
The reason this is null is because of the sequence of the pair of lines in the init function:
{code}
jQuery(document).ready(jQuery.proxy(this.initialize, this));
this.resizeEventName = "resize.rf.edt." + this.id;
{code}
When the EDT is first intialized, the _initialize_ callback isn't invoked until the ready event is fired - after the _resizeEventName_ property has been set. However after an AJAX update, the _ready_ callback's are invoked immediately, hence the empty resizeEventName property.
In resolving this issue we should *both* re-order the LoCs, as well as implement the null check recommended by [~moosetraveller].
> ExtendedDataTable Sorting resets $(window).resize Events
> --------------------------------------------------------
>
> Key: RF-13117
> URL: https://issues.jboss.org/browse/RF-13117
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.3
> Environment: Tomcat 7
> JBoss 7.1
> Reporter: Thomas Zuberbuehler
> Assignee: Brian Leathem
> Labels: regression
> Fix For: 4.3.4
>
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> Sorting removes other resize events.
> At some point following code is called:
> {code}
> // extendedDataTable.js
> deActivateResizeListener: function() {
> $(window).off(this.resizeEventName);
> }
> {code}
> Notice that this.resizeEventName is undefined.
> Before code is invoked (Chrome JavaScript console)
> {code}
> $._data(window,'events').resize
> [Object, Object]
> {code}
> After invoking
> {code}
> $._data(window,'events').resize
> TypeError: Cannot read property 'resize' of undefined
> {code}
> http://stackoverflow.com/questions/18045891/how-to-check-if-onresize-meth...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months