[JBoss JIRA] (RF-13673) Backport the plain skin fix from RF 5
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13673?page=com.atlassian.jira.plugin.s... ]
Juraj Húska reopened RF-13673:
------------------------------
Reopening the issue because setting of plain skin breaks components visual state.
Please see attachments with screenshots for autocomplete or for calendar.
> Backport the plain skin fix from RF 5
> -------------------------------------
>
> Key: RF-13673
> URL: https://issues.jboss.org/browse/RF-13673
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: skinning
> Reporter: Brian Leathem
> Assignee: Brian Leathem
> Fix For: 4.5.0.Alpha3
>
> Attachments: autocompleteInPlain.png, calendarWithPlain.png
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> Backport RF-11103.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months
[JBoss JIRA] (RF-13724) Showcase - leftovers of old Editor skinning setup cause 404 error
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13724?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13724:
-------------------------------
Fix Version/s: 4.5.0.Beta1
> Showcase - leftovers of old Editor skinning setup cause 404 error
> -----------------------------------------------------------------
>
> Key: RF-13724
> URL: https://issues.jboss.org/browse/RF-13724
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: showcase
> Affects Versions: 4.5.0.Alpha3
> Reporter: Juraj Húska
> Priority: Trivial
> Fix For: 4.5.0.Beta1
>
>
> In the example for editor advanced configuration, there is leftover of old skinning setup:
> {code:xml}
> <h:form>
> <a4j:outputPanel style="display:none">
> <rich:editor skin="kama" />
> <rich:editor skin="v2" />
> <rich:editor skin="office2003" />
> </a4j:outputPanel>
> </h:form>
> {code}
> This causes 404 HTTP errors, while those skins can not be found in the resources.
> Note that this errors do not affect any functionality nor they are somehow visible elsewhere than in JS console.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months
[JBoss JIRA] (RF-13723) fileUpload: 'Clear All' button does not work after maxFilesQuantity reached on IE
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13723?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13723:
-------------------------------
Fix Version/s: 4.5.0.Beta1
> fileUpload: 'Clear All' button does not work after maxFilesQuantity reached on IE
> ---------------------------------------------------------------------------------
>
> Key: RF-13723
> URL: https://issues.jboss.org/browse/RF-13723
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.5.0.Alpha3
> Environment: IE 11, IE 10
> Reporter: Jiří Štefek
> Priority: Minor
> Labels: IE10, IE11
> Fix For: 4.5.0.Beta1
>
>
> The 'Clear All' button does nothing when clicked after maxFilesQuantity reached by adding items using the 'Add' button. It works after items were added by DnD.
> You have to click somewhere on the page, to get the button working.
> It works fine in FF, Chrome.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months
[JBoss JIRA] (RF-11093) UIDataAdaptor context variable backup broken (reentrance problem)
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RF-11093?page=com.atlassian.jira.plugin.s... ]
Matej Novotny commented on RF-11093:
------------------------------------
[~bleathem] I am trying to verify this issue but I am not sure how to create a reproducer/how to verify this.
Steps to reproduce aren't much help, I can't see what is meant by "visiting component's tree" in commandLink.
Could you please give me some hint?
> UIDataAdaptor context variable backup broken (reentrance problem)
> -----------------------------------------------------------------
>
> Key: RF-11093
> URL: https://issues.jboss.org/browse/RF-11093
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.0.0.Final
> Environment: Windows XP, Java 6, Tomcat 6.0.24, Mojarra 2.0.2.
> Reporter: Yannick Valot
> Assignee: Yannick Valot
> Fix For: 4.5.0.Alpha3
>
> Attachments: UIDataAdaptor.java.patch
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> I am encountering a reentrance problem with org.richfaces.component.UIDataAdaptor (using it as a dataTable).
> I need to perform a visit of the component tree while executing an action on a command link in one row of the same table.
> {code}
> <rich:dataTable value="#{listOfItems}" var="myItem" >
> ... some stuff here ...
> <commandLink here>
> ... some stuff here ...
> </rich:dataTable>
> {code}
> After the action on the command link has visited the component tree, myItem is no longer available in context.
> When the UIDataAdaptor sets or resets the "myItem" context variable, it backs up any previous value by calling captureOrigValue(FacesContext), and later restores it by calling restoreOrigValue(FacesContext), but it looks as if the visit backs the variable up twice (in a nested fashion), and it erases myItem between the two backups :
> - backup variable (old value is correctly backed up) (in visitTree(VisitContext visitContext, VisitCallback callback))
> - erase variable (setRowKey(facesContext, null) in same function)
> - erase variable (doVisitChildren(VisitContext context, boolean visitRows))
> - erase variable (visitTree(VisitContext visitContext, VisitCallback callback))
> - backup variable (erases backed up value) (walk(FacesContext faces, DataVisitor visitor, Object argument))
> - ...
> - restore value (restores null) (walk(FacesContext faces, DataVisitor visitor, Object argument))
> - restore value (restores null) (in visitTree(VisitContext visitContext, VisitCallback callback))
> etc.
> The problem can be solved by *stacking* backed up variables, instead of storing them in a simple attribute, to allow for any kind of reentrance.
> (I do not say that this is the best possible patch, but it has solved the problem for me).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 3 months
[JBoss JIRA] (RF-13691) EDT in uiRepeat - selection corrupted in multiple paged table
by Martin Tomasek (JIRA)
[ https://issues.jboss.org/browse/RF-13691?page=com.atlassian.jira.plugin.s... ]
Martin Tomasek updated RF-13691:
--------------------------------
Environment: WildFly 8.1.
> EDT in uiRepeat - selection corrupted in multiple paged table
> -------------------------------------------------------------
>
> Key: RF-13691
> URL: https://issues.jboss.org/browse/RF-13691
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.5.0.Alpha3
> Environment: WildFly 8.1.
> Reporter: Juraj Húska
> Assignee: Brian Leathem
> Labels: regression
> Fix For: 4.5.0.Alpha3
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> When {{EDT}} is in {{uiRepeat}} and has multiple pages, then selection of rows functionality does not work as expected.
> It seems that there is a problem with row indices. Please see steps to reproduce.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (RF-13691) EDT in uiRepeat - selection corrupted in multiple paged table
by Martin Tomasek (JIRA)
[ https://issues.jboss.org/browse/RF-13691?page=com.atlassian.jira.plugin.s... ]
Martin Tomasek edited comment on RF-13691 at 7/14/14 10:07 AM:
---------------------------------------------------------------
We can still reproduce issue but only on WildFly 8.1. with JSF 2.2. Component works fine on EAP 6.3. with JSF < 2.2. We also tried functionality on a5ee6651647f2f07ca89aca6946d3f7b79d967ea and behaviour was the same as I described before. Works on EAP 6.3. didn't work on WildFly 8.1.
was (Author: mtomasek):
We can still reproduce issue but only on Wildfly 8.1. with JSF 2.2. Component works fine on EAP 6.3. with JSF < 2.2. We also tried functionality on a5ee6651647f2f07ca89aca6946d3f7b79d967ea and behaviour was the same as I described before. Works on EAP 6.3. didn't work on Wildfly 8.1.
> EDT in uiRepeat - selection corrupted in multiple paged table
> -------------------------------------------------------------
>
> Key: RF-13691
> URL: https://issues.jboss.org/browse/RF-13691
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.5.0.Alpha3
> Reporter: Juraj Húska
> Assignee: Brian Leathem
> Labels: regression
> Fix For: 4.5.0.Alpha3
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> When {{EDT}} is in {{uiRepeat}} and has multiple pages, then selection of rows functionality does not work as expected.
> It seems that there is a problem with row indices. Please see steps to reproduce.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (RF-13690) DataTable in uiRepeat - scrolling in table makes columns unsorted again
by Martin Tomasek (JIRA)
[ https://issues.jboss.org/browse/RF-13690?page=com.atlassian.jira.plugin.s... ]
Martin Tomasek edited comment on RF-13690 at 7/14/14 10:07 AM:
---------------------------------------------------------------
We can still reproduce issue but only on WildFly 8.1. with JSF 2.2. Component works fine on EAP 6.3. with JSF < 2.2. We also tried functionality on a5ee6651647f2f07ca89aca6946d3f7b79d967ea and behaviour was the same as I described before. Works on EAP 6.3. didn't work on WildFly 8.1.
was (Author: mtomasek):
We can still reproduce issue but only on Wildfly 8.1. with JSF 2.2. Component works fine on EAP 6.3. with JSF < 2.2. We also tried functionality on a5ee6651647f2f07ca89aca6946d3f7b79d967ea and behaviour was the same as I described before. Works on EAP 6.3. didn't work on Wildfly 8.1.
> DataTable in uiRepeat - scrolling in table makes columns unsorted again
> -----------------------------------------------------------------------
>
> Key: RF-13690
> URL: https://issues.jboss.org/browse/RF-13690
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.5.0.Alpha3
> Environment: WildFly 8.1.
> Reporter: Juraj Húska
> Assignee: Brian Leathem
> Labels: regression
> Fix For: 4.5.0.Alpha3
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> When {{DataTable}} is nested in {{uiRepeat}}, then scrolling over the table with {{dataScroller}} makes sorting according to some column broken - the columns are unsorted.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (RF-13690) DataTable in uiRepeat - scrolling in table makes columns unsorted again
by Martin Tomasek (JIRA)
[ https://issues.jboss.org/browse/RF-13690?page=com.atlassian.jira.plugin.s... ]
Martin Tomasek updated RF-13690:
--------------------------------
Environment: WildFly 8.1.
> DataTable in uiRepeat - scrolling in table makes columns unsorted again
> -----------------------------------------------------------------------
>
> Key: RF-13690
> URL: https://issues.jboss.org/browse/RF-13690
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.5.0.Alpha3
> Environment: WildFly 8.1.
> Reporter: Juraj Húska
> Assignee: Brian Leathem
> Labels: regression
> Fix For: 4.5.0.Alpha3
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> When {{DataTable}} is nested in {{uiRepeat}}, then scrolling over the table with {{dataScroller}} makes sorting according to some column broken - the columns are unsorted.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (RF-13691) EDT in uiRepeat - selection corrupted in multiple paged table
by Martin Tomasek (JIRA)
[ https://issues.jboss.org/browse/RF-13691?page=com.atlassian.jira.plugin.s... ]
Martin Tomasek edited comment on RF-13691 at 7/14/14 10:04 AM:
---------------------------------------------------------------
We can still reproduce issue but only on Wildfly 8.1. with JSF 2.2. Component works fine on EAP 6.3. with JSF < 2.2. We also tried functionality on a5ee6651647f2f07ca89aca6946d3f7b79d967ea and behaviour was the same as I described before. Works on EAP 6.3. didn't work on Wildfly 8.1.
was (Author: mtomasek):
We can still reproduce issue. Steps to reproduce are exactly the same as before. We also tried functionality on commit a5ee6651647f2f07ca89aca6946d3f7b79d967ea and we were able to reproduce the issue.
> EDT in uiRepeat - selection corrupted in multiple paged table
> -------------------------------------------------------------
>
> Key: RF-13691
> URL: https://issues.jboss.org/browse/RF-13691
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.5.0.Alpha3
> Reporter: Juraj Húska
> Assignee: Brian Leathem
> Labels: regression
> Fix For: 4.5.0.Alpha3
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> When {{EDT}} is in {{uiRepeat}} and has multiple pages, then selection of rows functionality does not work as expected.
> It seems that there is a problem with row indices. Please see steps to reproduce.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months