November 2011 - richfaces-planning-issues

[JBoss JIRA] (RFPL-1732) Component reference: collapsible panel contains wrong description of facets

by Brian Leathem (Updated) (JIRA)

[ https://issues.jboss.org/browse/RFPL-1732?page=com.atlassian.jira.plugin.... ] Brian Leathem updated RFPL-1732: -------------------------------- Priority: Minor (was: Major) > Component reference: collapsible panel contains wrong description of facets > --------------------------------------------------------------------------- > > Key: RFPL-1732 > URL: https://issues.jboss.org/browse/RFPL-1732 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.0.0.Final > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Priority: Minor > Fix For: 4.1.0.CR1 > > > http://docs.jboss.org/richfaces/nightly_4_0_X/Component_Reference/en-US/h... > Section "9.3.3. Appearance" in Component Reference contains wrong information about facets of rich:collapsiblePanel. Method UICollapsiblePanel.getFacetCount() return 0 so maybe this section can be removed. -- 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

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RFPL-1732) Component reference: collapsible panel contains wrong description of facets

by Brian Leathem (Resolved) (JIRA)

[ https://issues.jboss.org/browse/RFPL-1732?page=com.atlassian.jira.plugin.... ] Brian Leathem resolved RFPL-1732. --------------------------------- Resolution: Done > Component reference: collapsible panel contains wrong description of facets > --------------------------------------------------------------------------- > > Key: RFPL-1732 > URL: https://issues.jboss.org/browse/RFPL-1732 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.0.0.Final > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 4.1.0.CR1 > > > http://docs.jboss.org/richfaces/nightly_4_0_X/Component_Reference/en-US/h... > Section "9.3.3. Appearance" in Component Reference contains wrong information about facets of rich:collapsiblePanel. Method UICollapsiblePanel.getFacetCount() return 0 so maybe this section can be removed. -- 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

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RFPL-1732) Component reference: collapsible panel contains wrong description of facets

by Brian Leathem (Commented) (JIRA)

[ https://issues.jboss.org/browse/RFPL-1732?page=com.atlassian.jira.plugin.... ] Brian Leathem commented on RFPL-1732: ------------------------------------- >From the docs, we currently have the line: {quote} The headerExpandedClass and headerCollapsedClass facets are used to style the appearance of the panel when it is expanded and collapsed respectively. {quote} This should be changed to: {quote} The headerExpanded and headerCollapsed CSS classes are used to style the appearance of the panel when it is expanded and collapsed respectively. {quote} ---- After that, there is the line: {quote} The expandControl facet defines the content in the panel header used for expanding, and the collapseControl facet defines the content in the panel header used for collapsing. {quote} These _facets_ are not currently supported, and this line should be removed. ---- @dkocher Indeed, these facets do seem to be useful. If you would like to see them implemented, please file a new RF jira requesting the feature. > Component reference: collapsible panel contains wrong description of facets > --------------------------------------------------------------------------- > > Key: RFPL-1732 > URL: https://issues.jboss.org/browse/RFPL-1732 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.0.0.Final > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 4.1.0.CR1 > > > http://docs.jboss.org/richfaces/nightly_4_0_X/Component_Reference/en-US/h... > Section "9.3.3. Appearance" in Component Reference contains wrong information about facets of rich:collapsiblePanel. Method UICollapsiblePanel.getFacetCount() return 0 so maybe this section can be removed. -- 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

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RFPL-1495) popupPanel: documentation omits forms requirement and contains wrong sample

by Brian Leathem (Resolved) (JIRA)

[ https://issues.jboss.org/browse/RFPL-1495?page=com.atlassian.jira.plugin.... ] Brian Leathem resolved RFPL-1495. --------------------------------- Resolution: Done Updated the popupPanel documentation, with details of embedding a form, or attaching to an exsiting form's DOM element. Removed the form element from the popupPanel example. > popupPanel: documentation omits forms requirement and contains wrong sample > --------------------------------------------------------------------------- > > Key: RFPL-1495 > URL: https://issues.jboss.org/browse/RFPL-1495 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.0.0.Final > Reporter: Ilya Shaikovsky > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.1.0.CR1 > > > http://docs.jboss.org/richfaces/latest_4_0_X/Component_Reference/en-US/ht... > 1) That note: > {quote} > "Placement > The <rich:popupPanel> component is usually rendered in front of any other objects on the page. This is achieved by attaching the component to the <body> element of the page, and setting a very high "z-index" (t" > {quote} > actually have to be followed by one more critical note. > {quote} > "Limitation: defined by default popup *has to* have form element inside and not to be nested to external form in order submitting components/behaviors inside to work properly (because of repositioning in DOM). And to be able to be nested domElementAttachment should be changed to either form or parent." > {quote} > 2) Example 9.2. <rich:popupPanel> example > confuses as form is around the panel! it should be either removed at all(as that sample not requires submission) or moved inside. -- 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

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RFPL-1495) popupPanel: documentation omits forms requirement and contains wrong sample

by Brian Leathem (Updated) (JIRA)

[ https://issues.jboss.org/browse/RFPL-1495?page=com.atlassian.jira.plugin.... ] Brian Leathem updated RFPL-1495: -------------------------------- Description: http://docs.jboss.org/richfaces/latest_4_0_X/Component_Reference/en-US/ht... 1) That note: {quote} "Placement The <rich:popupPanel> component is usually rendered in front of any other objects on the page. This is achieved by attaching the component to the <body> element of the page, and setting a very high "z-index" (t" {quote} actually have to be followed by one more critical note. {quote} "Limitation: defined by default popup *has to* have form element inside and not to be nested to external form in order submitting components/behaviors inside to work properly (because of repositioning in DOM). And to be able to be nested domElementAttachment should be changed to either form or parent." {quote} 2) Example 9.2. <rich:popupPanel> example confuses as form is around the panel! it should be either removed at all(as that sample not requires submission) or moved inside. was: http://docs.jboss.org/richfaces/latest_4_0_X/Component_Reference/en-US/ht... 1) That note: "Placement The <rich:popupPanel> component is usually rendered in front of any other objects on the page. This is achieved by attaching the component to the <body> element of the page, and setting a very high "z-index" (t" actually have to be followed by one more critical note. "Limitation: defined by default popup *has to* have form element inside and not to be nested to external form in order submitting components/behaviors inside to work properly (because of repositioning in DOM). And to be able to be nested domElementAttachment should be changed to either form or parent." 2) Example 9.2. <rich:popupPanel> example confuses as form is around the panel! it should be either removed at all(as that sample not requires submission) or moved inside. > popupPanel: documentation omits forms requirement and contains wrong sample > --------------------------------------------------------------------------- > > Key: RFPL-1495 > URL: https://issues.jboss.org/browse/RFPL-1495 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.0.0.Final > Reporter: Ilya Shaikovsky > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.1.0.CR1 > > > http://docs.jboss.org/richfaces/latest_4_0_X/Component_Reference/en-US/ht... > 1) That note: > {quote} > "Placement > The <rich:popupPanel> component is usually rendered in front of any other objects on the page. This is achieved by attaching the component to the <body> element of the page, and setting a very high "z-index" (t" > {quote} > actually have to be followed by one more critical note. > {quote} > "Limitation: defined by default popup *has to* have form element inside and not to be nested to external form in order submitting components/behaviors inside to work properly (because of repositioning in DOM). And to be able to be nested domElementAttachment should be changed to either form or parent." > {quote} > 2) Example 9.2. <rich:popupPanel> example > confuses as form is around the panel! it should be either removed at all(as that sample not requires submission) or moved inside. -- 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

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RFPL-1393) Provide table's @keepSaved attribute documentation

by Brian Leathem (Assigned) (JIRA)

[ https://issues.jboss.org/browse/RFPL-1393?page=com.atlassian.jira.plugin.... ] Brian Leathem reassigned RFPL-1393: ----------------------------------- Assignee: Lukáš Fryč > Provide table's @keepSaved attribute documentation > -------------------------------------------------- > > Key: RFPL-1393 > URL: https://issues.jboss.org/browse/RFPL-1393 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.0.0.Final > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.1.0.CR1 > > -- 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

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RFPL-1498) Component reference: remove a4j:form

by Brian Leathem (Assigned) (JIRA)

[ https://issues.jboss.org/browse/RFPL-1498?page=com.atlassian.jira.plugin.... ] Brian Leathem reassigned RFPL-1498: ----------------------------------- Assignee: Brian Leathem > Component reference: remove a4j:form > ------------------------------------ > > Key: RFPL-1498 > URL: https://issues.jboss.org/browse/RFPL-1498 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.0.0.Final > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 4.1.0.CR1 > > > The component reference contains <a4j:form> on several places. Use <h:form> instead of <a4j:form>: > section 9.4.2. Showing and hiding the pop-up > section 9.4.5. Header and controls > section 13.4.2. Attaching the tool-tip to another component -- 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

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RFPL-1490) Component reference: fix file upload description

by Brian Leathem (Assigned) (JIRA)

[ https://issues.jboss.org/browse/RFPL-1490?page=com.atlassian.jira.plugin.... ] Brian Leathem reassigned RFPL-1490: ----------------------------------- Assignee: Brian Leathem > Component reference: fix file upload description > ------------------------------------------------ > > Key: RFPL-1490 > URL: https://issues.jboss.org/browse/RFPL-1490 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.0.0.Final > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 4.1.0.CR1 > > > The Component Reference should be updated because it contains following statement in file upload section. The attribute maxFilesQuantity has not been implemented yet in RichFaces 4 so it can be removed. > {quote} > To limit the maximum size of the uploaded files, define the byte size with the org.richfaces.fileUpload.maxRequestSizes context parameter of the web.xml settings file for the project. > {quote} -- 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

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RFPL-1477) Component reference: wrong examples for tooltip

by Brian Leathem (Assigned) (JIRA)

[ https://issues.jboss.org/browse/RFPL-1477?page=com.atlassian.jira.plugin.... ] Brian Leathem reassigned RFPL-1477: ----------------------------------- Assignee: Brian Leathem > Component reference: wrong examples for tooltip > ----------------------------------------------- > > Key: RFPL-1477 > URL: https://issues.jboss.org/browse/RFPL-1477 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.0.0.Final > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 4.1.0.CR1 > > > There are bugs in all examples for rich:tooltip > # rename rich:toolTip to rich:tooltip in all examples > # in Example 13.8. Defining tool-tip content the "Basic Content" sample doesn't work and probably will not work in RF 4.x (see RF-11002) > # in Example 13.9. Attaching the tool-tip put the content inside the component instead of using attribute value > # in Example 13.10. Unattached tool-tips put the content inside the component instead of using attribute value and fix attribute "onclick" of panel > {code:xml} > onclick="#{rich:component('toolTipId')}.show(event);" > {code} > # in Example 13.11. Advanced tool-tip usage put the content inside the component instead of using attribute value and change the direction attribute to "topRight" > # check the text that it describes the examples correctly -- 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

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RFPL-1495) popupPanel: documentation omits forms requirement and contains wrong sample

by Brian Leathem (Assigned) (JIRA)

[ https://issues.jboss.org/browse/RFPL-1495?page=com.atlassian.jira.plugin.... ] Brian Leathem reassigned RFPL-1495: ----------------------------------- Assignee: Brian Leathem > popupPanel: documentation omits forms requirement and contains wrong sample > --------------------------------------------------------------------------- > > Key: RFPL-1495 > URL: https://issues.jboss.org/browse/RFPL-1495 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.0.0.Final > Reporter: Ilya Shaikovsky > Assignee: Brian Leathem > Priority: Critical > Fix For: 4.1.0.CR1 > > > http://docs.jboss.org/richfaces/latest_4_0_X/Component_Reference/en-US/ht... > 1) That note: > "Placement > The <rich:popupPanel> component is usually rendered in front of any other objects on the page. This is achieved by attaching the component to the <body> element of the page, and setting a very high "z-index" (t" > actually have to be followed by one more critical note. > "Limitation: defined by default popup *has to* have form element inside and not to be nested to external form in order submitting components/behaviors inside to work properly (because of repositioning in DOM). And to be able to be nested domElementAttachment should be changed to either form or parent." > 2) Example 9.2. <rich:popupPanel> example > confuses as form is around the panel! it should be either removed at all(as that sample not requires submission) or moved inside. -- 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

14 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

richfaces-planning-issues November 2011