January 2013 - richfaces-planning-issues

[JBoss JIRA] (RFPL-1962) Component-Reference for rich:jQuery - Defining a selector section is untrue

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-1962?page=com.atlassian.jira.plugin.... ] Brian Leathem updated RFPL-1962: -------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > Component-Reference for rich:jQuery - Defining a selector section is untrue > --------------------------------------------------------------------------- > > Key: RFPL-1962 > URL: https://issues.jboss.org/browse/RFPL-1962 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.1.0.Final > Reporter: Lukáš Fryč > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Documentation [1] says: > {quote} > The selector attribute can refer to the id identifier of any JSF component or client. > {quote} > This is untrue, the real algorithm [2] is trying to expand each CSS ID selector (starting with {{#}}) from {{componentId}} to {{clientId}} (e.g. {{#component}} becomes {{#form\:component}}). > [1] http://docs.jboss.org/richfaces/4.1.X/4.1.0.Final/Component_Reference/en-... > [2] https://github.com/richfaces/components/blob/develop/common/ui/src/main/j... -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RFPL-2331) collapsible panel: add section about headerCollapsed and headerExpanded facets

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-2331?page=com.atlassian.jira.plugin.... ] Brian Leathem updated RFPL-2331: -------------------------------- Original Estimate: 45 minutes Remaining Estimate: 45 minutes > collapsible panel: add section about headerCollapsed and headerExpanded facets > ------------------------------------------------------------------------------- > > Key: RFPL-2331 > URL: https://issues.jboss.org/browse/RFPL-2331 > Project: RichFaces Planning > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.0.0.Final, 4.1.0.Final > Reporter: Lance Sloan > Labels: collapsiblePanel, docs, headerCollapsed, headerExpanded > Fix For: 4.3-Tracking > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > While attempting to use collapsiblePanels, I found it extremely frustrating that the "header" facet doesn't work for it like it does for most components. After searching, I learned from the forum that the facets to use are "headerCollapsed" and "headerExpanded". There's no mention of that in the documentation. Please update the documentation and examples. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RFPL-2101) panelToggleListener wrong description for attributes @type and @listener in VDL-DOC

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-2101?page=com.atlassian.jira.plugin.... ] Brian Leathem updated RFPL-2101: -------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > panelToggleListener wrong description for attributes @type and @listener in VDL-DOC > ----------------------------------------------------------------------------------- > > Key: RFPL-2101 > URL: https://issues.jboss.org/browse/RFPL-2101 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.2.0.Final > Reporter: Jiří Štefek > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Wrong description in VDL-doc [1] for attribute @type. As written in component reference [2] it accepts PanelToggleListener not ActionListener. > Wrong description in VDL-doc [1] for attribute @listener. As written in component reference [2] the method should accept PanelToggleEvent not ActionEvent. > [1]http://docs.jboss.org/richfaces/latest_4_2_X/vdldoc/rich/panelToggleLis... > [2]http://docs.jboss.org/richfaces/4.2.X/4.2.0.Final/Component_Reference/e... -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RFPL-2079) Component reference - rich:hotKey - small typos

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-2079?page=com.atlassian.jira.plugin.... ] Brian Leathem updated RFPL-2079: -------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > Component reference - rich:hotKey - small typos > ----------------------------------------------- > > Key: RFPL-2079 > URL: https://issues.jboss.org/browse/RFPL-2079 > Project: RichFaces Planning > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.2.0.Final > Environment: Component reference > Reporter: Juraj Húska > Priority: Trivial > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > I have found these small typos for _rich:hotKey in Component Reference_, which should be IMHO fixed: > CURRENT: attach it with selector attribute to all the elements defined using this selector. This attribute uses syntax for CSS rule selector defined by W3C consortium with some jQuery extensions. > MAYBE: *attach it to the specific elements by defining selector attribute*. This attribute uses syntax *of the CSS selectors* defined by W3C consortium with some jQuery extensions. *(e.g. which one ?)* > CURRENT: The key attribute defines the hot key itself which is processed by the component. > MAYBE: The key attribute defines the hot key *itself, which* is processed by the component. > CURRENT: The preventDefault attribute specifies whenever hot key binding should prevent default browser-specific actions to be taken (e.g. Ctrl+A hot key selecting all available text, Ctrl+B opening bookmarks bar, etc.). > MAYBE: The preventDefault attribute specifies *whether the* hot key binding should prevent default browser-specific actions to be taken (e.g. Ctrl+A hot key selecting all available text, Ctrl+B opening bookmarks bar, etc.). > CURRENT: keydown (default event) is fired when hot key sequence is initiated (keys are down) > MAYBE: keydown (default event) is fired when *the* hot key sequence is initiated (*the* keys are down) -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RFPL-2080) Developer guide - resource mapping/optimization - small typos

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-2080?page=com.atlassian.jira.plugin.... ] Brian Leathem updated RFPL-2080: -------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > Developer guide - resource mapping/optimization - small typos > ------------------------------------------------------------- > > Key: RFPL-2080 > URL: https://issues.jboss.org/browse/RFPL-2080 > Project: RichFaces Planning > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.2.0.Final > Environment: Developer guide > Reporter: Juraj Húska > Priority: Trivial > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > I have found these small typos in the _Developer guide_, for part dealing with _resource mapping/optimization_: > _RESOURCE OPTIMIZATION_ > CURRENT: resources are not compressed in a development and during an unit-test to enable a client-side debugging > MAYBE: resources are not compressed in a development *stage* and during *a unit-testing* to enable a client-side debugging > CURRENT: resources are compressed in a production and during a system-test to minimize a network bandwidth > MAYBE: resources are compressed in a production *stage* and during a *system-testing* to minimize a network bandwidth > _RESOURCE MAPPING_ > CURRENT: This feature can help to solve of following cases: > MAYBE: This feature can help to *solve following* cases: > CURRENT: providing alternative versions of a resource > MAYBE: providing alternative versions *of resources* > CURRENT: moving resources to servers with static content > MAYBE: moving resources to servers *serving* static content > _RESOURCE MAPPING CONFIGURATION FILE_ > CURRENT: A following sample shows a JSF resource with name resourceLibrary:resourceName relocated to a resource anotherResourceLibrary:anotherResourceName: > MAYBE: A following sample shows a JSF resource with *a* name resourceLibrary:resourceName relocated to a resource anotherResourceLibrary:anotherResourceName: > CURRENT: It is possible to define additional resource mapping configuration files using a contextual parameter identifying class-path locations where files resides: org.richfaces.resourceMapping.mappingFile (a comma-separated list of class-path files). > MAYBE: It is possible to define additional resource mapping configuration *files, by using* a contextual parameter identifying *the* class-path locations where files resides: org.richfaces.resourceMapping.mappingFile (a comma-separated list of *the* class-path files). -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RFPL-2078) Component reference - a4j:push - small typos

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-2078?page=com.atlassian.jira.plugin.... ] Brian Leathem updated RFPL-2078: -------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > Component reference - a4j:push - small typos > -------------------------------------------- > > Key: RFPL-2078 > URL: https://issues.jboss.org/browse/RFPL-2078 > Project: RichFaces Planning > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.2.0.Final > Environment: Component reference > Reporter: Juraj Húska > Priority: Trivial > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > I have found these typos and other things which should be IMHO corrected for the _a4j:push_ in _Component Reference_. > CURRENT: When you are registering Push servlet in the Servlets 3.0 environments manually, the RichFaces will detect that servlet for Push is already registered and it avoids to initialize it again. > However be sure to setup the Push servlet to support asynchronous requests - modify the servlet registration in the previous web.xml snippet as follows: > MAYBE: When you *attempt to register* Push servlet *manually* in the Servlets 3.0 environments, the RichFaces will detect that servlet for Push is already registered*, and* it *avoids initializing* it again. > *However, be sure* to setup the Push servlet to support asynchronous requests - modify the servlet registration *from* the previous web.xml snippet as follows: > CURRENT: Sending a message using the TopicsContext involves creating a TopicKey instance (denominator of given message topic) and looking up the TopicsContext used for topic registration and message publishing. > MAYBE: Sending a message using the TopicsContext*, which was used for registration of topic and message publishing,* involves creating a TopicKey instance (denominator of given message topic) and *look the TopicContext up*. > CURRENT: Ensure the Create durable subscriber and Delete durable subscriber options are set to true for push functionality. > MAYBE: Ensure the Create durable subscriber and *the* Delete durable subscriber options are set to true for *proper* push functionality. > CURRENT: The RichFaces looks for the JMS Connection Factory on the JNDI context /ConnectionFactory by default > MAYBE: The RichFaces looks for the JMS Connection Factory on the JNDI context /ConnectionFactory by *default.* > CURRENT: The JMS message which should be propagated to Push needs to be created with method session.createObjectMessage(message);. > MAYBE: The JMS message which should be propagated to Push needs to be created with *the* method session.createObjectMessage(message);. > CURRENT: Receiving messages from JMS doesn't differ from receiving messages sent by the TopicsContext or using CDI events. > MAYBE: Receiving messages from *a JMS queues* doesn't differ from *the* receiving messages sent by the TopicsContext or using a CDI events. > CURRENT: This example demonstrates a simple use of the <a4j:push> causing an immediate update of page content. > MAYBE: *The example above* demonstrates a simple use of the <a4j:push> causing an immediate update of *the* page content. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RFPL-2583) Metamer: rewrite DnD tests using webDriver

by Ján Jamrich (JIRA)

Ján Jamrich created RFPL-2583: --------------------------------- Summary: Metamer: rewrite DnD tests using webDriver Key: RFPL-2583 URL: https://issues.jboss.org/browse/RFPL-2583 Project: RichFaces Planning Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Ján Jamrich Assignee: Ján Jamrich Since DnD impl has changed tests start failing and fix them would require comparable resources than rewrite them completely using webDriver. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RFPL-2516) Editor - submitting by a4j:commandButton causes JS error

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RFPL-2516?page=com.atlassian.jira.plugin.... ] Juraj Húska commented on RFPL-2516: ----------------------------------- Resolved by using {{StringEscapeUtils.escapeJavaScript}} on both {{newVal}} and {{oldVal}}. See [this|https://github.com/richfaces/qa/commit/51fe30a17bf2614e2c22b770ba248...] commit. > Editor - submitting by a4j:commandButton causes JS error > -------------------------------------------------------- > > Key: RFPL-2516 > URL: https://issues.jboss.org/browse/RFPL-2516 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 4.1.0.Milestone2 > Environment: RichFaces 4.1.0-SNAPSHOT r.d0f9c11eb0dacc1444c0a3182b12567e28aef6bc > Metamer 4.1.0-SNAPSHOT r.22610 > Apache MyFaces JSF-2.1 Core Impl 2.1.1 > Apache Tomcat 6.0.32 > OpenJDK Runtime Environment 1.6.0_22-b22 @Linux > Internet Explorer 8.0 @ Win32 > RichFaces 4.1.0-SNAPSHOT r.d0f9c11eb0dacc1444c0a3182b12567e28aef6bc > Metamer 4.1.0-SNAPSHOT r.22610 > Apache MyFaces JSF-2.1 Core Impl 2.1.1 > Apache Tomcat 6.0.32 > OpenJDK Runtime Environment 1.6.0_22-b22 @Linux > Firefox 5.0 @ Linux x86_64 > Reporter: Jan Papousek > Assignee: Pavol Pitonak > Priority: Optional > Fix For: 4.3.0.CR1 > > > When the rich:editor is submitted by a4j:commandButton which renders an output area, the output area stays empty. This can be reproduced in Metamer - faces/components/richEditor/simple.xhtml. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RFPL-2516) Editor - submitting by a4j:commandButton causes JS error

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RFPL-2516?page=com.atlassian.jira.plugin.... ] Juraj Húska resolved RFPL-2516. ------------------------------- Resolution: Done > Editor - submitting by a4j:commandButton causes JS error > -------------------------------------------------------- > > Key: RFPL-2516 > URL: https://issues.jboss.org/browse/RFPL-2516 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 4.1.0.Milestone2 > Environment: RichFaces 4.1.0-SNAPSHOT r.d0f9c11eb0dacc1444c0a3182b12567e28aef6bc > Metamer 4.1.0-SNAPSHOT r.22610 > Apache MyFaces JSF-2.1 Core Impl 2.1.1 > Apache Tomcat 6.0.32 > OpenJDK Runtime Environment 1.6.0_22-b22 @Linux > Internet Explorer 8.0 @ Win32 > RichFaces 4.1.0-SNAPSHOT r.d0f9c11eb0dacc1444c0a3182b12567e28aef6bc > Metamer 4.1.0-SNAPSHOT r.22610 > Apache MyFaces JSF-2.1 Core Impl 2.1.1 > Apache Tomcat 6.0.32 > OpenJDK Runtime Environment 1.6.0_22-b22 @Linux > Firefox 5.0 @ Linux x86_64 > Reporter: Jan Papousek > Assignee: Pavol Pitonak > Priority: Optional > Fix For: 4.3.0.CR1 > > > When the rich:editor is submitted by a4j:commandButton which renders an output area, the output area stays empty. This can be reproduced in Metamer - faces/components/richEditor/simple.xhtml. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RFPL-2516) Editor - submitting by a4j:commandButton causes JS error

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RFPL-2516?page=com.atlassian.jira.plugin.... ] Juraj Húska edited comment on RFPL-2516 at 1/3/13 9:21 AM: ----------------------------------------------------------- The submitted value is altered by CKEditor and it is not in our hands. We should probably somehow escape the submitted value before logging by Metamer to the page, because that is what is failing. was (Author: jhuska): The submitted value is altered by CKEditor and it is not in our hands. We should probably somehow escape the submitted value before logging by Metamer to the console, because that is what is failing. > Editor - submitting by a4j:commandButton causes JS error > -------------------------------------------------------- > > Key: RFPL-2516 > URL: https://issues.jboss.org/browse/RFPL-2516 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 4.1.0.Milestone2 > Environment: RichFaces 4.1.0-SNAPSHOT r.d0f9c11eb0dacc1444c0a3182b12567e28aef6bc > Metamer 4.1.0-SNAPSHOT r.22610 > Apache MyFaces JSF-2.1 Core Impl 2.1.1 > Apache Tomcat 6.0.32 > OpenJDK Runtime Environment 1.6.0_22-b22 @Linux > Internet Explorer 8.0 @ Win32 > RichFaces 4.1.0-SNAPSHOT r.d0f9c11eb0dacc1444c0a3182b12567e28aef6bc > Metamer 4.1.0-SNAPSHOT r.22610 > Apache MyFaces JSF-2.1 Core Impl 2.1.1 > Apache Tomcat 6.0.32 > OpenJDK Runtime Environment 1.6.0_22-b22 @Linux > Firefox 5.0 @ Linux x86_64 > Reporter: Jan Papousek > Assignee: Pavol Pitonak > Priority: Optional > Fix For: 4.3.0.CR1 > > > When the rich:editor is submitted by a4j:commandButton which renders an output area, the output area stays empty. This can be reproduced in Metamer - faces/components/richEditor/simple.xhtml. -- 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

11 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

richfaces-planning-issues January 2013