[JBoss JIRA] (RF-12929) PickList change event not firing correctly when ordering objects in target area
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-12929?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak commented on RF-12929:
------------------------------------
Verified in 4.3.4, it's ready to be closed.
> PickList change event not firing correctly when ordering objects in target area
> -------------------------------------------------------------------------------
>
> Key: RF-12929
> URL: https://issues.jboss.org/browse/RF-12929
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 4.3.0.Final
> Environment: JBoss AS 7
> Reporter: Simon Plangger
> Assignee: Domenico Giannotta
> Labels: event, onchange, pickList
> Fix For: 4.3.4
>
>
> The *change* event is not firing, when moving an element from the target area (selected side) to the top or to the bottom of the list. There is no problem with moving items and the change event as long as you don't make it the first or last entry.
> To reproduce:
> {code}
> <rich:pickList
> onchange="alert('changed')"
> orderable="true"
> >
> <f:selectItem itemLabel="test 1" itemValue="test 1" />
> <f:selectItem itemLabel="test 2" itemValue="test 2" />
> <f:selectItem itemLabel="test 3" itemValue="test 3" />
> <f:selectItem itemLabel="test 4" itemValue="test 4" />
> <f:selectItem itemLabel="test 5" itemValue="test 5" />
> </rich:pickList>
> {code}
> Just *select all* items and move them around.
--
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-12784) Showcase readme - update deployment from eclipse part
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-12784?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak commented on RF-12784:
------------------------------------
Verified in 4.3.4, it's ready to be closed.
> Showcase readme - update deployment from eclipse part
> -----------------------------------------------------
>
> Key: RF-12784
> URL: https://issues.jboss.org/browse/RF-12784
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: doc, showcase
> Affects Versions: 4.3.0.Final, 5-Tracking
> Reporter: Juraj Húska
> Assignee: Juraj Húska
> Priority: Trivial
> Fix For: 4.3.4, 5.0.0.Alpha2
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> The deployment of the showcase from eclipse needs to be written down in in more details, because it is not trivial:
> An user needs to be aware of:
> * select correct maven profile
> * alter the deployment assembly
> * be aware of wrong context root load in the eclipse browser
> I will send pull request for this one.
--
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-12345) JS error when pressing ESC on an open inplaceSelect in IE
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-12345?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak commented on RF-12345:
------------------------------------
Verified in 4.3.4 in IE8, IE9, and IE9. It's ready to be closed.
> JS error when pressing ESC on an open inplaceSelect in IE
> ---------------------------------------------------------
>
> Key: RF-12345
> URL: https://issues.jboss.org/browse/RF-12345
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 4.2.2.Final
> Environment: Internet Explorer 8 and 9
> Reporter: Moshe Elisha
> Assignee: Domenico Giannotta
> Labels: ie, inplaceselect
> Fix For: 4.3.4
>
>
> Open an inplaceSelect list - when pressing ESC while the list is open, you will get a JavaScript error " Unable to get value of the property 'value': object is null or undefined" (Reproduced with IE 8 and 9 on the RichFaces showcase).
--
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-13116) Using filters with paging / default filter value in extendeddatatable
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13116?page=com.atlassian.jira.plugin.s... ]
Juraj Húska resolved RF-13116.
------------------------------
Resolution: Rejected
Rejecting the issue, as we agreed with the reporter that it is not a bug.
> Using filters with paging / default filter value in extendeddatatable
> ---------------------------------------------------------------------
>
> Key: RF-13116
> URL: https://issues.jboss.org/browse/RF-13116
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: John Strandmyr
> Priority: Critical
> Labels: datascroller, extendedDataTable, filter
>
> I've got an extededdatatable from richfaces and if i add a default value to the filter, so that some rows are excluded on first rendering, and then change the filter to show the rows that were hidden, I don't get any calls to the actionlisteners on the rows that were hidden at first.
> It works fine on those rows that was shown in the first page load, but not on those hidden.
> The same issue appears when i use paging, and some rows are on page two. if i use the filter to show some rows from another page, the actionlistener isnt triggered. I can still click on those rows that was apparent on the first page, but not on the other pages.
> If I don't have a default filter, or a pager, i can add and remove filtering and everything is fine.
> {code}
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <html xmlns="http://www.w3.org/1999/xhtml"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:f="http://java.sun.com/jsf/core"
> xmlns:a4j="http://richfaces.org/a4j"
> xmlns:rich="http://richfaces.org/rich">
> <h:head>
> <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
> <h:outputScript name="jsf.js" library="javax.faces"/>
> </h:head>
> <h:body>
> <h:form>
> <rich:extendedDataTable value="#{tiltakServer.tiltak}" var="tiltak" id="tiltakTable">
> <rich:column filter="#{tiltakFilter.tittelImpl}">
> <f:facet name="header">
> <h:outputText value="Tittel" />
> <h:panelGroup styleClass="filter">
> <h:inputText value="#{tiltakFilter.tittelFilter}">
> <a4j:ajax event="keyup" render="tiltakTable@body" execute="@this"/>
> </h:inputText>
> </h:panelGroup>
> </f:facet>
> <h:outputText value="#{tiltak.tittel}"/>
> </rich:column>
> <rich:column>
> <f:facet name="header">
> Edit
> </f:facet>
> <h:commandLink value="Goto">
> <f:actionListener type="no.hmskontoret.hmskontoret.hendelsesregister.TiltakOnEditActionListener"/>
> </h:commandLink>
> </rich:column>
> </rich:extendedDataTable>
> </h:form>
> </h:body>
> </html>
> {code}
--
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-13116) Using filters with paging / default filter value in extendeddatatable
by John Strandmyr (JIRA)
[ https://issues.jboss.org/browse/RF-13116?page=com.atlassian.jira.plugin.s... ]
John Strandmyr commented on RF-13116:
-------------------------------------
Yes this was correct. Using either the javax.face.bean.SessionScoped with the @ManagedBean or using javax.enterprice.context.SessionScoped with @Named were both issue-fixers.
This can be considered solved. Thanks for great response on this matter. Sorry if I should have angled things differently before registering to Jira.
> Using filters with paging / default filter value in extendeddatatable
> ---------------------------------------------------------------------
>
> Key: RF-13116
> URL: https://issues.jboss.org/browse/RF-13116
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: John Strandmyr
> Priority: Critical
> Labels: datascroller, extendedDataTable, filter
>
> I've got an extededdatatable from richfaces and if i add a default value to the filter, so that some rows are excluded on first rendering, and then change the filter to show the rows that were hidden, I don't get any calls to the actionlisteners on the rows that were hidden at first.
> It works fine on those rows that was shown in the first page load, but not on those hidden.
> The same issue appears when i use paging, and some rows are on page two. if i use the filter to show some rows from another page, the actionlistener isnt triggered. I can still click on those rows that was apparent on the first page, but not on the other pages.
> If I don't have a default filter, or a pager, i can add and remove filtering and everything is fine.
> {code}
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <html xmlns="http://www.w3.org/1999/xhtml"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:f="http://java.sun.com/jsf/core"
> xmlns:a4j="http://richfaces.org/a4j"
> xmlns:rich="http://richfaces.org/rich">
> <h:head>
> <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
> <h:outputScript name="jsf.js" library="javax.faces"/>
> </h:head>
> <h:body>
> <h:form>
> <rich:extendedDataTable value="#{tiltakServer.tiltak}" var="tiltak" id="tiltakTable">
> <rich:column filter="#{tiltakFilter.tittelImpl}">
> <f:facet name="header">
> <h:outputText value="Tittel" />
> <h:panelGroup styleClass="filter">
> <h:inputText value="#{tiltakFilter.tittelFilter}">
> <a4j:ajax event="keyup" render="tiltakTable@body" execute="@this"/>
> </h:inputText>
> </h:panelGroup>
> </f:facet>
> <h:outputText value="#{tiltak.tittel}"/>
> </rich:column>
> <rich:column>
> <f:facet name="header">
> Edit
> </f:facet>
> <h:commandLink value="Goto">
> <f:actionListener type="no.hmskontoret.hmskontoret.hendelsesregister.TiltakOnEditActionListener"/>
> </h:commandLink>
> </rich:column>
> </rich:extendedDataTable>
> </h:form>
> </h:body>
> </html>
> {code}
--
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-13116) Using filters with paging / default filter value in extendeddatatable
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13116?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-13116:
-----------------------------
Assignee: (was: Juraj Húska)
> Using filters with paging / default filter value in extendeddatatable
> ---------------------------------------------------------------------
>
> Key: RF-13116
> URL: https://issues.jboss.org/browse/RF-13116
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: John Strandmyr
> Priority: Critical
> Labels: datascroller, extendedDataTable, filter
>
> I've got an extededdatatable from richfaces and if i add a default value to the filter, so that some rows are excluded on first rendering, and then change the filter to show the rows that were hidden, I don't get any calls to the actionlisteners on the rows that were hidden at first.
> It works fine on those rows that was shown in the first page load, but not on those hidden.
> The same issue appears when i use paging, and some rows are on page two. if i use the filter to show some rows from another page, the actionlistener isnt triggered. I can still click on those rows that was apparent on the first page, but not on the other pages.
> If I don't have a default filter, or a pager, i can add and remove filtering and everything is fine.
> {code}
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <html xmlns="http://www.w3.org/1999/xhtml"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:f="http://java.sun.com/jsf/core"
> xmlns:a4j="http://richfaces.org/a4j"
> xmlns:rich="http://richfaces.org/rich">
> <h:head>
> <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
> <h:outputScript name="jsf.js" library="javax.faces"/>
> </h:head>
> <h:body>
> <h:form>
> <rich:extendedDataTable value="#{tiltakServer.tiltak}" var="tiltak" id="tiltakTable">
> <rich:column filter="#{tiltakFilter.tittelImpl}">
> <f:facet name="header">
> <h:outputText value="Tittel" />
> <h:panelGroup styleClass="filter">
> <h:inputText value="#{tiltakFilter.tittelFilter}">
> <a4j:ajax event="keyup" render="tiltakTable@body" execute="@this"/>
> </h:inputText>
> </h:panelGroup>
> </f:facet>
> <h:outputText value="#{tiltak.tittel}"/>
> </rich:column>
> <rich:column>
> <f:facet name="header">
> Edit
> </f:facet>
> <h:commandLink value="Goto">
> <f:actionListener type="no.hmskontoret.hmskontoret.hendelsesregister.TiltakOnEditActionListener"/>
> </h:commandLink>
> </rich:column>
> </rich:extendedDataTable>
> </h:form>
> </h:body>
> </html>
> {code}
--
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-13116) Using filters with paging / default filter value in extendeddatatable
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13116?page=com.atlassian.jira.plugin.s... ]
Juraj Húska edited comment on RF-13116 at 8/22/13 6:02 AM:
-----------------------------------------------------------
I have reproduced the behavior from the user provided code. It is pushed in this [branch|https://github.com/richfaces/richfaces-qa/tree/RF-13116].
However, I believe it is not a bug.
The user provided code for filter ({{TiltakFilter}}) is mixing CDI bean annotation {{javax.enterprise.context.SessionScoped}} with the faces one.
I guess it is made accidentally, and user want to use JSF backing beans.
If I use either JSF beans or CDI beans only then it works correctly.
[~strandmyr], could you please confirm this ? Could you change the import to the: {{javax.faces.bean.SessionScoped}} ?
was (Author: jhuska):
I have reproduced the behavior from the user provided code. It is pushed in this [branch|https://github.com/richfaces/richfaces-qa/tree/RF-13116].
However, I believe it is not a bug.
The user provided code for filter ({{TiltakFilter}}) is mixing CDI bean annotation {{javax.enterprise.context.SessionScoped}} with the faces one.
I guess it is made accidentally, and user want to use JSF backing beans.
If I use either JSF beans or CDI beans only then it works correctly.
[~strandmyr], could you please confirm this ? Can you change the import to the: {{javax.faces.bean.SessionScoped}} ?
> Using filters with paging / default filter value in extendeddatatable
> ---------------------------------------------------------------------
>
> Key: RF-13116
> URL: https://issues.jboss.org/browse/RF-13116
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: John Strandmyr
> Priority: Critical
> Labels: datascroller, extendedDataTable, filter
>
> I've got an extededdatatable from richfaces and if i add a default value to the filter, so that some rows are excluded on first rendering, and then change the filter to show the rows that were hidden, I don't get any calls to the actionlisteners on the rows that were hidden at first.
> It works fine on those rows that was shown in the first page load, but not on those hidden.
> The same issue appears when i use paging, and some rows are on page two. if i use the filter to show some rows from another page, the actionlistener isnt triggered. I can still click on those rows that was apparent on the first page, but not on the other pages.
> If I don't have a default filter, or a pager, i can add and remove filtering and everything is fine.
> {code}
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <html xmlns="http://www.w3.org/1999/xhtml"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:f="http://java.sun.com/jsf/core"
> xmlns:a4j="http://richfaces.org/a4j"
> xmlns:rich="http://richfaces.org/rich">
> <h:head>
> <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
> <h:outputScript name="jsf.js" library="javax.faces"/>
> </h:head>
> <h:body>
> <h:form>
> <rich:extendedDataTable value="#{tiltakServer.tiltak}" var="tiltak" id="tiltakTable">
> <rich:column filter="#{tiltakFilter.tittelImpl}">
> <f:facet name="header">
> <h:outputText value="Tittel" />
> <h:panelGroup styleClass="filter">
> <h:inputText value="#{tiltakFilter.tittelFilter}">
> <a4j:ajax event="keyup" render="tiltakTable@body" execute="@this"/>
> </h:inputText>
> </h:panelGroup>
> </f:facet>
> <h:outputText value="#{tiltak.tittel}"/>
> </rich:column>
> <rich:column>
> <f:facet name="header">
> Edit
> </f:facet>
> <h:commandLink value="Goto">
> <f:actionListener type="no.hmskontoret.hmskontoret.hendelsesregister.TiltakOnEditActionListener"/>
> </h:commandLink>
> </rich:column>
> </rich:extendedDataTable>
> </h:form>
> </h:body>
> </html>
> {code}
--
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-13116) Using filters with paging / default filter value in extendeddatatable
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13116?page=com.atlassian.jira.plugin.s... ]
Juraj Húska commented on RF-13116:
----------------------------------
I have reproduced the behavior from the user provided code. It is pushed in this [branch|https://github.com/richfaces/richfaces-qa/tree/RF-13116].
However, I believe it is not a bug.
The user provided code for filter ({{TiltakFilter}}) is mixing CDI bean annotation {{javax.enterprise.context.SessionScoped}} with the faces one.
I guess it is made accidentally, and user want to use JSF backing beans.
If I use either JSF beans or CDI beans only then it works correctly.
[~strandmyr], could you please confirm this ? Can you change the import to the: {{javax.faces.bean.SessionScoped}} ?
> Using filters with paging / default filter value in extendeddatatable
> ---------------------------------------------------------------------
>
> Key: RF-13116
> URL: https://issues.jboss.org/browse/RF-13116
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: John Strandmyr
> Assignee: Juraj Húska
> Priority: Critical
> Labels: datascroller, extendedDataTable, filter
>
> I've got an extededdatatable from richfaces and if i add a default value to the filter, so that some rows are excluded on first rendering, and then change the filter to show the rows that were hidden, I don't get any calls to the actionlisteners on the rows that were hidden at first.
> It works fine on those rows that was shown in the first page load, but not on those hidden.
> The same issue appears when i use paging, and some rows are on page two. if i use the filter to show some rows from another page, the actionlistener isnt triggered. I can still click on those rows that was apparent on the first page, but not on the other pages.
> If I don't have a default filter, or a pager, i can add and remove filtering and everything is fine.
> {code}
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <html xmlns="http://www.w3.org/1999/xhtml"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:f="http://java.sun.com/jsf/core"
> xmlns:a4j="http://richfaces.org/a4j"
> xmlns:rich="http://richfaces.org/rich">
> <h:head>
> <meta http-equiv="content-type" content="text/html; charset=utf-8"/>
> <h:outputScript name="jsf.js" library="javax.faces"/>
> </h:head>
> <h:body>
> <h:form>
> <rich:extendedDataTable value="#{tiltakServer.tiltak}" var="tiltak" id="tiltakTable">
> <rich:column filter="#{tiltakFilter.tittelImpl}">
> <f:facet name="header">
> <h:outputText value="Tittel" />
> <h:panelGroup styleClass="filter">
> <h:inputText value="#{tiltakFilter.tittelFilter}">
> <a4j:ajax event="keyup" render="tiltakTable@body" execute="@this"/>
> </h:inputText>
> </h:panelGroup>
> </f:facet>
> <h:outputText value="#{tiltak.tittel}"/>
> </rich:column>
> <rich:column>
> <f:facet name="header">
> Edit
> </f:facet>
> <h:commandLink value="Goto">
> <f:actionListener type="no.hmskontoret.hmskontoret.hendelsesregister.TiltakOnEditActionListener"/>
> </h:commandLink>
> </rich:column>
> </rich:extendedDataTable>
> </h:form>
> </h:body>
> </html>
> {code}
--
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 Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-11275?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak commented on RF-11275:
------------------------------------
Verified in 4.3.4, it's ready to be closed.
> 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
> Assignee: Brian Leathem
> 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