January 2013 - richfaces-planning-issues

[JBoss JIRA] (RFPL-2694) Developer guide - ajaxbegin, ajaxbeforedomupdate, and ajaxcomplete events corrections

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-2694?page=com.atlassian.jira.plugin.... ] Brian Leathem updated RFPL-2694: -------------------------------- Sprint: 4.3.0.Final Doc Sprint > Developer guide - ajaxbegin, ajaxbeforedomupdate, and ajaxcomplete events corrections > ------------------------------------------------------------------------------------- > > Key: RFPL-2694 > URL: https://issues.jboss.org/browse/RFPL-2694 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.3.0.CR1 > Reporter: Juraj Húska > Assignee: Brian Leathem > Fix For: 4.3.0.Final > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > If I understand things correctly it should be: > *current:* {{ajaxbeforedomupdate}}: triggered after Ajax response has been returned but before the DOM tree of the browser has been updated. > *should be:* {{ajaxbeforedomupdate}}: triggered after *an* Ajax response has been returned but before the DOM tree of the browser *will be* updated. > *current:* {{ajaxcomplete}}: triggered after Ajax response has been returned and the DOM tree of the browser has been updated. > *should be:* {{ajaxcomplete}}: triggered after *an* Ajax response *was* returned and the DOM tree of the browser has been updated. > Previous examples also miss *an* article before Ajax word. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RFPL-2592) Example 9.7. Keyword-based switching in Component Referance Guide has wrong value @previous

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-2592?page=com.atlassian.jira.plugin.... ] Brian Leathem updated RFPL-2592: -------------------------------- Sprint: 4.3.0.CR1 Doc Corrections, 4.3.0.Final Doc Sprint (was: 4.3.0.CR1 Doc Corrections) > Example 9.7. Keyword-based switching in Component Referance Guide has wrong value @previous > ------------------------------------------------------------------------------------------- > > Key: RFPL-2592 > URL: https://issues.jboss.org/browse/RFPL-2592 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.2.2.Final > Reporter: Mark Bloomfield > Assignee: Brian Leathem > Priority: Minor > Fix For: 4.3.0.Final > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > In the component referacne guide Example 9.7 the example states the value @previous as the keyword to use to switch to a previous panel. I believe it should be @prev as per the online example. > The bug is in the text prior to the example and in the example itself. > Please note I am new to RichFaces so perhaps it's wrong in the component? However I have tested with @prev and it works. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RFPL-2692) Component reference - focus component corrections

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-2692?page=com.atlassian.jira.plugin.... ] Brian Leathem updated RFPL-2692: -------------------------------- Sprint: 4.3.0.Final Doc Sprint > Component reference - focus component corrections > ------------------------------------------------- > > Key: RFPL-2692 > URL: https://issues.jboss.org/browse/RFPL-2692 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.3.0.CR1 > Reporter: Juraj Húska > Assignee: Brian Leathem > Fix For: 4.3.0.Final > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Reopening and proposing small adjustments: > *current:* The <rich:focus> component allows one to focus components on a page. It is intended to be used with any input field. > *maybe:* The <rich:focus> component allows one to *automatically* focus components on a page. It is intended to be used with any input field. > *current:* If no component is invalid, then first component in the form will be focused. > *maybe*: If *all components are valid*, then *the* first component in the form *is focused*. > *current*: There is a mention on two places that "This configuration will take priority over any other focus setup". > *should be:* If both of {{preserve=true}} and {{FocusManager}} used in place, which one takes priority ? > *current*: Then it is possible to call the applyFocus() JavaScript API method in order to let the focus apply. > *should be*: Then it is possible to call the applyFocus() JavaScript API method in order to let the focus *be applied.* -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RFPL-2348) Document FileUpload: onfileselect and immediateUpload

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-2348?page=com.atlassian.jira.plugin.... ] Brian Leathem updated RFPL-2348: -------------------------------- Original Estimate: 45 minutes Remaining Estimate: 45 minutes > Document FileUpload: onfileselect and immediateUpload > ----------------------------------------------------- > > Key: RFPL-2348 > URL: https://issues.jboss.org/browse/RFPL-2348 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.3.0.M2 > Reporter: Lukáš Fryč > Priority: Minor > Fix For: 4.3.0.Final > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RFPL-1921) Document partial table rendering targets @body, etc.

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-1921?page=com.atlassian.jira.plugin.... ] Brian Leathem updated RFPL-1921: -------------------------------- Original Estimate: 1 hour, 30 minutes Remaining Estimate: 1 hour, 30 minutes > Document partial table rendering targets @body, etc. > ---------------------------------------------------- > > Key: RFPL-1921 > URL: https://issues.jboss.org/browse/RFPL-1921 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.1.0.CR1 > Reporter: Lukáš Fryč > Fix For: 4.3.0.Final > > Original Estimate: 1 hour, 30 minutes > Remaining Estimate: 1 hour, 30 minutes > > In Component Reference, there is described only {{@rows(...)}} target [1]. > But the {{table@body}} also works. > Provide complete documentation on all possible table-specific targets. > Additionally make sure that these targets are tested properly, > and provide the blog. > [1] http://docs.jboss.org/richfaces/latest_4_1_X/Component_Reference/en-US/ht... -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RFPL-2693) Component reference - placeholder component correction

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-2693?page=com.atlassian.jira.plugin.... ] Brian Leathem updated RFPL-2693: -------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > Component reference - placeholder component correction > ------------------------------------------------------ > > Key: RFPL-2693 > URL: https://issues.jboss.org/browse/RFPL-2693 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.3.0.CR1 > Reporter: Juraj Húska > Assignee: Brian Leathem > Fix For: 4.3.0.Final > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > I am missing style classes reference. There is {{rf-plhdr}} class int the {{placeholder.css}}. > I would also add to the part mentioning the {{selector}} attribute a reference to the part of document where it is defined how to use this attribute (it has some tricky parts). -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RFPL-2265) Update the docs to remove browser version numbers, and link to the browser compatibility matrix

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-2265?page=com.atlassian.jira.plugin.... ] Brian Leathem updated RFPL-2265: -------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > Update the docs to remove browser version numbers, and link to the browser compatibility matrix > ----------------------------------------------------------------------------------------------- > > Key: RFPL-2265 > URL: https://issues.jboss.org/browse/RFPL-2265 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: doc > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.3.0.Final > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > The RichFaces devloper guide specifies versions of browsers against which the components are expected to work. > http://docs.jboss.org/richfaces/latest_4_X/Developer_Guide/en-US/html/cha... > This is a duplicate of the information maintined in the wiki: > https://community.jboss.org/wiki/PrioritizedRichFacesBrowsersCompatibilit... > I propose simplifying the Developer guide to list only the supported browsers, but not their versions. We would then link to the relevant wiki page from the developer guide for those looking for information on specific versions. > The alternative to this is to be more rigorous about keeping the two docs in synch with every release. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RFPL-2694) Developer guide - ajaxbegin, ajaxbeforedomupdate, and ajaxcomplete events corrections

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-2694?page=com.atlassian.jira.plugin.... ] Brian Leathem updated RFPL-2694: -------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > Developer guide - ajaxbegin, ajaxbeforedomupdate, and ajaxcomplete events corrections > ------------------------------------------------------------------------------------- > > Key: RFPL-2694 > URL: https://issues.jboss.org/browse/RFPL-2694 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.3.0.CR1 > Reporter: Juraj Húska > Assignee: Brian Leathem > Fix For: 4.3.0.Final > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > If I understand things correctly it should be: > *current:* {{ajaxbeforedomupdate}}: triggered after Ajax response has been returned but before the DOM tree of the browser has been updated. > *should be:* {{ajaxbeforedomupdate}}: triggered after *an* Ajax response has been returned but before the DOM tree of the browser *will be* updated. > *current:* {{ajaxcomplete}}: triggered after Ajax response has been returned and the DOM tree of the browser has been updated. > *should be:* {{ajaxcomplete}}: triggered after *an* Ajax response *was* returned and the DOM tree of the browser has been updated. > Previous examples also miss *an* article before Ajax word. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RFPL-2692) Component reference - focus component corrections

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-2692?page=com.atlassian.jira.plugin.... ] Brian Leathem updated RFPL-2692: -------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > Component reference - focus component corrections > ------------------------------------------------- > > Key: RFPL-2692 > URL: https://issues.jboss.org/browse/RFPL-2692 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.3.0.CR1 > Reporter: Juraj Húska > Assignee: Brian Leathem > Fix For: 4.3.0.Final > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > Reopening and proposing small adjustments: > *current:* The <rich:focus> component allows one to focus components on a page. It is intended to be used with any input field. > *maybe:* The <rich:focus> component allows one to *automatically* focus components on a page. It is intended to be used with any input field. > *current:* If no component is invalid, then first component in the form will be focused. > *maybe*: If *all components are valid*, then *the* first component in the form *is focused*. > *current*: There is a mention on two places that "This configuration will take priority over any other focus setup". > *should be:* If both of {{preserve=true}} and {{FocusManager}} used in place, which one takes priority ? > *current*: Then it is possible to call the applyFocus() JavaScript API method in order to let the focus apply. > *should be*: Then it is possible to call the applyFocus() JavaScript API method in order to let the focus *be applied.* -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RFPL-1921) Document partial table rendering targets @body, etc.

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-1921?page=com.atlassian.jira.plugin.... ] Brian Leathem updated RFPL-1921: -------------------------------- Sprint: (was: 4.3.0.CR2 Blog Sprint) > Document partial table rendering targets @body, etc. > ---------------------------------------------------- > > Key: RFPL-1921 > URL: https://issues.jboss.org/browse/RFPL-1921 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 4.1.0.CR1 > Reporter: Lukáš Fryč > Fix For: 4.3.0.Final > > > In Component Reference, there is described only {{@rows(...)}} target [1]. > But the {{table@body}} also works. > Provide complete documentation on all possible table-specific targets. > Additionally make sure that these targets are tested properly, > and provide the blog. > [1] http://docs.jboss.org/richfaces/latest_4_1_X/Component_Reference/en-US/ht... -- 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, 5 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