November 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13393) orderingList: JavaScript api is bound to wrong element

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RF-13393?page=com.atlassian.jira.plugin.s... ] Jiří Štefek updated RF-13393: ----------------------------- Fix Version/s: 5.0.0.Alpha2 > orderingList: JavaScript api is bound to wrong element > ------------------------------------------------------ > > Key: RF-13393 > URL: https://issues.jboss.org/browse/RF-13393 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Jiří Štefek > Priority: Critical > Fix For: 5.0.0.Alpha2 > > -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13393) orderingList: JavaScript api is bound to wrong element

by Jiří Štefek (JIRA)

Jiří Štefek created RF-13393: -------------------------------- Summary: orderingList: JavaScript api is bound to wrong element Key: RF-13393 URL: https://issues.jboss.org/browse/RF-13393 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-selects Affects Versions: 5.0.0.Alpha2 Reporter: Jiří Štefek Priority: Critical -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13392) TreeSelectionChangeEvent always triggered during Apply Request Phase

by Andreas Hahne (JIRA)

[ https://issues.jboss.org/browse/RF-13392?page=com.atlassian.jira.plugin.s... ] Andreas Hahne updated RF-13392: ------------------------------- Attachment: tree.zip Attached a simple Maven project demonstrating the effect. > TreeSelectionChangeEvent always triggered during Apply Request Phase > -------------------------------------------------------------------- > > Key: RF-13392 > URL: https://issues.jboss.org/browse/RF-13392 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tree > Affects Versions: 4.3.3 > Reporter: Andreas Hahne > Labels: richfaces, selectionChangeListener, tree > Attachments: tree.zip > > > When selecting a {{rich:treeNode}}, the corresponding {{selectionChangeListener}} is triggered during Apply Request Phase, no matter if the immediate attribute is set to true or false. > This leads to a weird behaviour in our application where an output panel is filled with the data selected in the tree. Both components are located in the same {{h:form}} element (in contrast to the showcase on the RF homepage). While the value of the {{h:outputText}} component is updated correctly, the one in the {{h:inputText}} is not because it is overwritten by the old value during Update Model Phase. If the change was processed during Invoke Application Phase this would not occur most likely. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-12930) Rename RichFaces.$ to less ambiguous RichFaces.component

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RF-12930?page=com.atlassian.jira.plugin.s... ] Matej Novotny closed RF-12930. ------------------------------ Verified > Rename RichFaces.$ to less ambiguous RichFaces.component > -------------------------------------------------------- > > Key: RF-12930 > URL: https://issues.jboss.org/browse/RF-12930 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core > Reporter: Brian Leathem > Assignee: Lukáš Fryč > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Possibly rename it to RichFaces.findComponent -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13251) FocusManager to support complex components like rich:autocomplete

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13251?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13251: --------------------------------- Immo, could you please give it one more try and see whether {{focusManager.focus("autocomplete")}} works or not? > FocusManager to support complex components like rich:autocomplete > ----------------------------------------------------------------- > > Key: RF-13251 > URL: https://issues.jboss.org/browse/RF-13251 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Assignee: Lukáš Fryč > Priority: Minor > Labels: waiting_on_user > > Currently the FocusManager in Richfaces only works on 'simple' UI components like h:inputText or h:selectOneMenu but not on more complex components like rich:autocomplete. > It would be good if FocusManager could support complex components or 'real' Ids as generated for that page. > The use case for the support on autocomplete is like this: > User has to enter multiple 'entities'. A rich:autocomplete is used to select the entity and add it to a list. After each ajax submit the focus gets lost and the user has to manually set the focus back to the autocomplete input field. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13251) FocusManager to support complex components like rich:autocomplete

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13251?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-13251 at 11/28/13 5:18 AM: ----------------------------------------------------------- Hey Immo, you shouldn't try to put focus on input itself, but rather use the component. Focus component itself will determine what to focus inside the target component. Here is the alghoritm: 1. determine {{focusCandidates}} (that's what FocusManager, focus preserve or others do) 2. look for {{:tabbable}} elements under candidates 3. select first {{:tabbable}} candidate element If we have similar DOM: {code} <div id="autocomplete"> <input id="autocompleteInput" /> </div> {code} you have focus candidate {{autocomplete}} (known on server as a client ID) (step 1), and you build list of actual candidate elements as {{[ 'autocompleteInput' ]}} (step 2), and use the first of them: {{autocompleteInput}} (step 3). See the implementation here: https://github.com/richfaces/richfaces/blob/master/framework/src/main/res... ---- In other words, use 'autocomplete' as a focus ID. You can access RichFaces client-side log to see what's happening. was (Author: lfryc): Hey Immo, you shouldn't try to put focus on input itself, but rather use the component. Focus component itself will determine what to focus inside the component. Here is the alghoritm: 1. determine {{focusCandidates}} (that's what FocusManager, focus preserve or others do) 2. look for {{:tabbable}} elements under candidates 3. select first {{:tabbable}} candidate element If we have similar DOM: {code} <div id="autocomplete"> <input id="autocompleteInput" /> </div> {code} you have focus candidate {{autocomplete}} (known on server as a client ID) (step 1), and you build list of actual candidate elements as {{[ 'autocompleteInput' ]}} (step 2), and use the first of them: {{autocompleteInput}} (step 3). See the implementation here: https://github.com/richfaces/richfaces/blob/master/framework/src/main/res... ---- In other words, use 'autocomplete' as a focus ID. You can access RichFaces client-side log to see what's happening. > FocusManager to support complex components like rich:autocomplete > ----------------------------------------------------------------- > > Key: RF-13251 > URL: https://issues.jboss.org/browse/RF-13251 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Assignee: Lukáš Fryč > Priority: Minor > Labels: waiting_on_user > > Currently the FocusManager in Richfaces only works on 'simple' UI components like h:inputText or h:selectOneMenu but not on more complex components like rich:autocomplete. > It would be good if FocusManager could support complex components or 'real' Ids as generated for that page. > The use case for the support on autocomplete is like this: > User has to enter multiple 'entities'. A rich:autocomplete is used to select the entity and add it to a list. After each ajax submit the focus gets lost and the user has to manually set the focus back to the autocomplete input field. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13251) FocusManager to support complex components like rich:autocomplete

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13251?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13251: --------------------------------- Hey Immo, you shouldn't try to put focus on input itself, but rather use the component. Focus component itself will determine what to focus inside the component. Here is the alghoritm: 1. determine {{focusCandidates}} (that's what FocusManager, focus preserve or others do) 2. look for {{:tabbable}} elements under candidates 3. select first {{:tabbable}} candidate element If we have similar DOM: {code} <div id="autocomplete"> <input id="autocompleteInput" /> </div> {code} you have focus candidate {{autocomplete}} (known on server as a client ID) (step 1), and you build list of actual candidate elements as {{[ 'autocompleteInput' ]}} (step 2), and use the first of them: {{autocompleteInput}} (step 3). See the implementation here: https://github.com/richfaces/richfaces/blob/master/framework/src/main/res... ---- In other words, use 'autocomplete' as a focus ID. You can access RichFaces client-side log to see what's happening. > FocusManager to support complex components like rich:autocomplete > ----------------------------------------------------------------- > > Key: RF-13251 > URL: https://issues.jboss.org/browse/RF-13251 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Assignee: Lukáš Fryč > Priority: Minor > Labels: waiting_on_user > > Currently the FocusManager in Richfaces only works on 'simple' UI components like h:inputText or h:selectOneMenu but not on more complex components like rich:autocomplete. > It would be good if FocusManager could support complex components or 'real' Ids as generated for that page. > The use case for the support on autocomplete is like this: > User has to enter multiple 'entities'. A rich:autocomplete is used to select the entity and add it to a list. After each ajax submit the focus gets lost and the user has to manually set the focus back to the autocomplete input field. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13265) Add RichFaces UI 4.5 dist module for generating ZIP distribution

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RF-13265?page=com.atlassian.jira.plugin.s... ] Matej Novotny closed RF-13265. ------------------------------ Verified, ZIP distribution is created correctly. > Add RichFaces UI 4.5 dist module for generating ZIP distribution > ---------------------------------------------------------------- > > Key: RF-13265 > URL: https://issues.jboss.org/browse/RF-13265 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 4.5.0.Alpha1 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.5.0.Alpha1 > > Original Estimate: 45 minutes > Remaining Estimate: 45 minutes > > It should distribute at least following artifacts: > - richfaces-components-a4j > - richfaces-components-rich -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13251) FocusManager to support complex components like rich:autocomplete

by Immo Benjes (JIRA)

[ https://issues.jboss.org/browse/RF-13251?page=com.atlassian.jira.plugin.s... ] Immo Benjes commented on RF-13251: ---------------------------------- Hi Lukáš, If you have a autocomplete component with the id="autocomplete" the actual generated code does not have an input field with the id="autocomplete". It has some subIds. The preserve focus might work but if you want to assign the focus with the focusManager it does not work. I have tried using focusManager.focus("autocomplete") (does not work) and focusManager.focus("autocomplete_input") (or similar can't remember the subID the actual input field has) but this doesn't work either. > FocusManager to support complex components like rich:autocomplete > ----------------------------------------------------------------- > > Key: RF-13251 > URL: https://issues.jboss.org/browse/RF-13251 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Assignee: Lukáš Fryč > Priority: Minor > Labels: waiting_on_user > > Currently the FocusManager in Richfaces only works on 'simple' UI components like h:inputText or h:selectOneMenu but not on more complex components like rich:autocomplete. > It would be good if FocusManager could support complex components or 'real' Ids as generated for that page. > The use case for the support on autocomplete is like this: > User has to enter multiple 'entities'. A rich:autocomplete is used to select the entity and add it to a list. After each ajax submit the focus gets lost and the user has to manually set the focus back to the autocomplete input field. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13362) ajax.reslib and base-component.reslib conflicts with RF 5.0 versions

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RF-13362?page=com.atlassian.jira.plugin.s... ] Matej Novotny closed RF-13362. ------------------------------ Verified > ajax.reslib and base-component.reslib conflicts with RF 5.0 versions > -------------------------------------------------------------------- > > Key: RF-13362 > URL: https://issues.jboss.org/browse/RF-13362 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.5.0.Alpha1 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.5.0.Alpha1 > > -- 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

10 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues November 2013