[JBoss JIRA] Updated: (RFPL-1477) Component reference: wrong examples for tooltip
by Jay Balunas (JIRA)
[ https://issues.jboss.org/browse/RFPL-1477?page=com.atlassian.jira.plugin.... ]
Jay Balunas updated RFPL-1477:
------------------------------
Fix Version/s: 4.1.0.CR1
(was: 4.1.0.Final)
> 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
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] Updated: (RFPL-1495) popupPanel: documentation omits forms requirement and contains wrong sample
by Jay Balunas (JIRA)
[ https://issues.jboss.org/browse/RFPL-1495?page=com.atlassian.jira.plugin.... ]
Jay Balunas updated RFPL-1495:
------------------------------
Fix Version/s: 4.1.0.CR1
(was: 4.1.0.Final)
> 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
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] Updated: (RFPL-1490) Component reference: fix file upload description
by Jay Balunas (JIRA)
[ https://issues.jboss.org/browse/RFPL-1490?page=com.atlassian.jira.plugin.... ]
Jay Balunas updated RFPL-1490:
------------------------------
Fix Version/s: 4.1.0.CR1
(was: 4.1.0.Final)
> 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
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months