[JBoss JIRA] Created: (RFPL-1423) fix grammatical issues
by Juraj Huska (JIRA)
fix grammatical issues
----------------------
Key: RFPL-1423
URL: https://issues.jboss.org/browse/RFPL-1423
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: examples
Affects Versions: 4.0.0.Final
Environment: richfaces-showcase
Reporter: Juraj Huska
Priority: Minor
a4j:status - sample: referenced status, there is adress instead of address
a4j:status - sample: status simple, there is succesfully instead of successfully
a4j:attachQueue - there is button with text label submit but the text above says that there should be button with label save
a4j:mediaOutput - all names of selects are Color1, but there should be Color1, Color2, Color3
rich:graphValidator - 1.in my opinion there should be the minimal and maximal length of password in the text which describes this component, 2. there is typo when passwords are typed correctly in info message, there is succesfully instead of successfully.
rich:message - in the text is written click "Validate" button, but there is "Ajax Validate" button
rich:messages - same as in rich:message
rich:dataTable - sample: DataTableFiltering - there is a filter for mileage, where is filter, which should filter values which are less than filter value, since there is < sign, but actually the filter works in a way less or equal.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Updated: (RFPL-1403) tables: discuss deprecation of sortMode attribute
by Jay Balunas (JIRA)
[ https://issues.jboss.org/browse/RFPL-1403?page=com.atlassian.jira.plugin.... ]
Jay Balunas updated RFPL-1403:
------------------------------
Fix Version/s: 4.1.0.Milestone1
Component/s: components
We need to remove confusing attributes like this, at least for now.
> tables: discuss deprecation of sortMode attribute
> -------------------------------------------------
>
> Key: RFPL-1403
> URL: https://issues.jboss.org/browse/RFPL-1403
> Project: RichFaces Planning
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: components
> Affects Versions: 4.0.0.Final
> Reporter: Ilya Shaikovsky
> Assignee: Ilya Shaikovsky
> Labels: requirements
> Fix For: 4.1.0.Milestone1
>
>
> sortMode has no sence now at all as there is no built-in sorting at the table. (used only with JS API now instead of isClear parameter - but why we need two ways for the same?)
> If we will create out-of-the-box functionality for sorting and will add some behaviors for doing sorting/filtering(instead of built in to table as in 3.3.x) - we could add something like isResetSorting flag to the control itself.
> I'm not 100% sure on that. So want to discuss.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Moved: (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 moved RF-11003 to RFPL-1477:
----------------------------------------
Project: RichFaces Planning (was: RichFaces)
Key: RFPL-1477 (was: RF-11003)
Affects Version/s: 4.0.0.Final
(was: 4.0.0.Final)
Component/s: doc
(was: doc)
Fix Version/s: 4.1.0.Milestone1
(was: 4.1.0.Milestone1)
> 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.Milestone1
>
>
> 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
14 years, 11 months