November 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-6573) Editor: scripts are not loading when appended by AJAX

by Nick Belaevski (JIRA)

Editor: scripts are not loading when appended by AJAX ----------------------------------------------------- Key: RF-6573 URL: https://jira.jboss.org/jira/browse/RF-6573 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.1 Reporter: Nick Belaevski Assignee: Pavel Yaschenko Priority: Minor Fix For: Future -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
2
0 / 0

[JBoss JIRA] (RF-12349) Calendar component hidden behind rich:accordian component

by Nikhil Hukkerikar (JIRA)

12 years

3
4
0 / 0

[JBoss JIRA] (RF-12616) Event re-targetting for correct javax.faces.source support

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12616: ------------------------------- Summary: Event re-targetting for correct javax.faces.source support Key: RF-12616 URL: https://issues.jboss.org/browse/RF-12616 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: core Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 4.3.0.M3 When processing events from components, attached AJAX behaviors propagates calls to: {code} jsf.ajax.request(source, event, options); {code} The ID of source element is then propagated to {{javax.faces.source}} as behavior event source. However when a source of a event wasn't root of the component's DOM, then {{javax.faces.source}} isn't equal to {{clientId}} of component and thus behavior decoding fails. ---- This issue can be fixed by incorporating interceptor for {{jsf.ajax.request}}, which will re-target source to the root of the component's DOM (which has attribute{{id}} equal to {{clientId}} of component). -- 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, 1 month

2
6
0 / 0

[JBoss JIRA] (RF-12556) maven help:describe for maven-cdk-plugin gets failed: String index out of range: -1

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12556?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12556: ------------------------------- Story Points: 0.5 > maven help:describe for maven-cdk-plugin gets failed: String index out of range: -1 > ----------------------------------------------------------------------------------- > > Key: RF-12556 > URL: https://issues.jboss.org/browse/RF-12556 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: cdk > Affects Versions: 4.0.0.Final, 4.1.0.Final, 4.2.0.Final, 4.2.1.Final > Reporter: Marek Novotny > Fix For: 4.3.0.M3 > > > Standard maven help for maven Mojo or Plugins fails on getting help for maven-cdk-plugin by running: > mvn help:describe -DgroupId=org.richfaces.cdk -DartifactId=maven-cdk-plugin -Dversion=4.2.1.Final -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (RF-12598) Diverge sorttaborder and focus jQuery plugins from focusManager.js

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12598: ------------------------------- Summary: Diverge sorttaborder and focus jQuery plugins from focusManager.js Key: RF-12598 URL: https://issues.jboss.org/browse/RF-12598 Project: RichFaces Issue Type: Sub-task Security Level: Public (Everyone can see) Components: component Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 4.3.0.M3 focusManager.js contains logic for sorting tabs and determining element to be focused. Those can be diverged as jQuery plugins to allow their reusing. -- 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, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (RF-10230) New component tracker for 4.X

by Jay Balunas (JIRA)

New component tracker for 4.X ----------------------------- Key: RF-10230 URL: https://issues.jboss.org/browse/RF-10230 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component Reporter: Jay Balunas This is an umbrella jira that can be used to link, and track to new component requests and plans for releases in the 4.X series. The complete process for handling new component requests, and discussions can be found here <LINK> When creating a new component jira please link here, or create as a sub-task of this jira. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
4
0 / 0

[JBoss JIRA] (RF-12605) Autocomplete Component Javascript Errors

by Jeff Smith (JIRA)

Jeff Smith created RF-12605: ------------------------------- Summary: Autocomplete Component Javascript Errors Key: RF-12605 URL: https://issues.jboss.org/browse/RF-12605 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component Affects Versions: 4.3.0.M2 Environment: Windows 7, Apache Tomcat 6 Reporter: Jeff Smith When testing the 4.3.0 M2 release, we're receiving javascript with the autocomplete component. These errors didn't occur in 4.2.2. 1. Autocomplete onblur event: We implemented simple javascript to uppercase the input value. The javascript code is "this.value=this.value.toUpperCase()". The error is: "TypeError:this.value is undefined" 2. Autocomplete destroy event: We have pages with multiple tabs that utilizes the autocomplete component. When switching from a tab that contains the autocomplete component, the tabs do not switch. The error we're receiving is: "ReferenceError:event is not defined" When clicking on the error in the FireFox error console, we're directed to the destroy function where the line of code is "this.__hide(event);". We attempting to complete a project that is critical to the users. We were testing the extended data table scrollbar fix, which is key to moving forward with the project. -- 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, 1 month

3
7
0 / 0

[JBoss JIRA] (RF-12114) Richfaces 4.2 rich:autocomplete don't fire ajax on blur event

by Ivan Costa (JIRA)

Ivan Costa created RF-12114: ------------------------------- Summary: Richfaces 4.2 rich:autocomplete don't fire ajax on blur event Key: RF-12114 URL: https://issues.jboss.org/browse/RF-12114 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core, component-input Affects Versions: 4.2.0.Final Environment: Richfaces 4.2 Final, Mojarra 2.1.7, Tomcat 7.0.26 Reporter: Ivan Costa rich:autocomplete don´t call actionListener on blur event -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

5
14
0 / 0

[JBoss JIRA] (RF-12535) RichFaces example generates warnings

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12535?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-12535. -------------------------------- Resolution: Incomplete Description Feel free to re-open this issue when you are able to provide a more meaningful description. > RichFaces example generates warnings > ------------------------------------ > > Key: RF-12535 > URL: https://issues.jboss.org/browse/RF-12535 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: Version: 6.0.0.Alpha2 > Build id: Alpha2-v20121004-2330-B40 > Build date: 20121004-2330 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 4.2.5 > > > The RichFaces example generates these warnings: > The local variable options may not have been initialized > slidfast.js > /jboss-richfaces-webapp/src/main/webapp/resources/js > line 60 > Missing semicolon > slidfast.js > /jboss-richfaces-webapp/src/main/webapp/resources/js > line 79 > Unnecessary @SuppressWarnings("unused") > Resources.java > /jboss-richfaces-webapp/src/main/java/org/jboss/tools/example/richfaces/util > line 26 > The local variable options may not have been initialized > slidfast.js > /jboss-richfaces-webapp/src/main/webapp/resources/js > line 57 > The local variable options may not have been initialized > slidfast.js > /jboss-richfaces-webapp/src/main/webapp/resources/js > line 58 > The local variable options may not have been initialized > slidfast.js > /jboss-richfaces-webapp/src/main/webapp/resources/js > line 54 > The local variable options may not have been initialized > slidfast.js > /jboss-richfaces-webapp/src/main/webapp/resources/js > line 56 > The import javax.inject.Inject is never used > RewriteConfigurationProvider.java > /jboss-richfaces-webapp/src/main/java/org/jboss/tools/example/richfaces/util > line 34 > The import javax.annotation.PostConstruct is never used > PageBean.java > /jboss-richfaces-webapp/src/main/java/org/jboss/tools/example/richfaces/controller > line 24 > The import javax.enterprise.inject.Model is never used > PageBean.java > /jboss-richfaces-webapp/src/main/java/org/jboss/tools/example/richfaces/controller > line 26 > The import javax.inject.Inject is never used > UserAgent.java > /jboss-richfaces-webapp/src/main/java/org/jboss/tools/example/richfaces/util > line 29 > No connection specified for project. No database-specific validation will be performed. > jboss-richfaces-webapp > The import javax.faces.bean.SessionScoped is never used UserAgent.java > /jboss-richfaces-webapp/src/main/java/org/jboss/tools/example/richfaces/util > line 27 > The import javax.faces.bean.ManagedBean is never used > UserAgent.java > /jboss-richfaces-webapp/src/main/java/org/jboss/tools/example/richfaces/util > line 26 -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (RF-12535) RichFaces example generates warnings

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12535?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12535: ------------------------------- Fix Version/s: (was: 4.3.0.M3) > RichFaces example generates warnings > ------------------------------------ > > Key: RF-12535 > URL: https://issues.jboss.org/browse/RF-12535 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: Version: 6.0.0.Alpha2 > Build id: Alpha2-v20121004-2330-B40 > Build date: 20121004-2330 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 4.2.5 > > > The RichFaces example generates these warnings: > The local variable options may not have been initialized > slidfast.js > /jboss-richfaces-webapp/src/main/webapp/resources/js > line 60 > Missing semicolon > slidfast.js > /jboss-richfaces-webapp/src/main/webapp/resources/js > line 79 > Unnecessary @SuppressWarnings("unused") > Resources.java > /jboss-richfaces-webapp/src/main/java/org/jboss/tools/example/richfaces/util > line 26 > The local variable options may not have been initialized > slidfast.js > /jboss-richfaces-webapp/src/main/webapp/resources/js > line 57 > The local variable options may not have been initialized > slidfast.js > /jboss-richfaces-webapp/src/main/webapp/resources/js > line 58 > The local variable options may not have been initialized > slidfast.js > /jboss-richfaces-webapp/src/main/webapp/resources/js > line 54 > The local variable options may not have been initialized > slidfast.js > /jboss-richfaces-webapp/src/main/webapp/resources/js > line 56 > The import javax.inject.Inject is never used > RewriteConfigurationProvider.java > /jboss-richfaces-webapp/src/main/java/org/jboss/tools/example/richfaces/util > line 34 > The import javax.annotation.PostConstruct is never used > PageBean.java > /jboss-richfaces-webapp/src/main/java/org/jboss/tools/example/richfaces/controller > line 24 > The import javax.enterprise.inject.Model is never used > PageBean.java > /jboss-richfaces-webapp/src/main/java/org/jboss/tools/example/richfaces/controller > line 26 > The import javax.inject.Inject is never used > UserAgent.java > /jboss-richfaces-webapp/src/main/java/org/jboss/tools/example/richfaces/util > line 29 > No connection specified for project. No database-specific validation will be performed. > jboss-richfaces-webapp > The import javax.faces.bean.SessionScoped is never used UserAgent.java > /jboss-richfaces-webapp/src/main/java/org/jboss/tools/example/richfaces/util > line 27 > The import javax.faces.bean.ManagedBean is never used > UserAgent.java > /jboss-richfaces-webapp/src/main/java/org/jboss/tools/example/richfaces/util > line 26 -- 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, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues November 2012