July 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13084) Change the autocomplete component to use the new autocomplete widget

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13084?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13084: --------------------------------- Hey Cody, POJO support are planned to be available for rich:select component, based probably on Select2: See e.g. "Auto Tokenization" sample from: http://ivaynberg.github.io/select2/ But rich:select should get full-fledge autocompletion/suggestioning functionality similar to autocomplete. I think it should also custom input and fallback code for manually added items: conversion of String to custom object. The main difference between autocomplete/select will be that autocomplete works with String, but > Change the autocomplete component to use the new autocomplete widget > -------------------------------------------------------------------- > > Key: RF-13084 > URL: https://issues.jboss.org/browse/RF-13084 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Reporter: Brian Leathem > Assignee: Lukáš Fryč > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 day > Remaining Estimate: 1 day > -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-13084) Change the autocomplete component to use the new autocomplete widget

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13084?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-13084 at 7/31/13 4:26 AM: ---------------------------------------------------------- Hey Cody, POJO support are planned to be available for rich:select component, based probably on Select2: See e.g. "Auto Tokenization" sample from: http://ivaynberg.github.io/select2/ But rich:select should get full-fledge autocompletion/suggestioning functionality similar to autocomplete. I think it should also custom input and fallback code for manually added items: conversion of String to custom object. The main difference between autocomplete/select will be that autocomplete works with String, but select works with objects. was (Author: lfryc): Hey Cody, POJO support are planned to be available for rich:select component, based probably on Select2: See e.g. "Auto Tokenization" sample from: http://ivaynberg.github.io/select2/ But rich:select should get full-fledge autocompletion/suggestioning functionality similar to autocomplete. I think it should also custom input and fallback code for manually added items: conversion of String to custom object. The main difference between autocomplete/select will be that autocomplete works with String, but > Change the autocomplete component to use the new autocomplete widget > -------------------------------------------------------------------- > > Key: RF-13084 > URL: https://issues.jboss.org/browse/RF-13084 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Reporter: Brian Leathem > Assignee: Lukáš Fryč > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 day > Remaining Estimate: 1 day > -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-13084) Change the autocomplete component to use the new autocomplete widget

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13084?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-13084 at 7/31/13 4:26 AM: ---------------------------------------------------------- Hey Cody, POJO support are planned to be available for rich:select component, based probably on Select2: See e.g. "Auto Tokenization" sample from: http://ivaynberg.github.io/select2/ But rich:select should get full-fledge autocompletion/suggestioning functionality similar to autocomplete. I think it should also custom input and fallback code for manually added items: conversion of String to custom object. The main difference between autocomplete/select will be that autocomplete works with String, but select works with objects. Let me know if you think it doesn't make sense. was (Author: lfryc): Hey Cody, POJO support are planned to be available for rich:select component, based probably on Select2: See e.g. "Auto Tokenization" sample from: http://ivaynberg.github.io/select2/ But rich:select should get full-fledge autocompletion/suggestioning functionality similar to autocomplete. I think it should also custom input and fallback code for manually added items: conversion of String to custom object. The main difference between autocomplete/select will be that autocomplete works with String, but select works with objects. > Change the autocomplete component to use the new autocomplete widget > -------------------------------------------------------------------- > > Key: RF-13084 > URL: https://issues.jboss.org/browse/RF-13084 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-input > Reporter: Brian Leathem > Assignee: Lukáš Fryč > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 day > Remaining Estimate: 1 day > -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-10793) ExtendedDataTable selection with Ctrl+click does not correctly update selection backing bean without clicking first

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-10793?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-10793: ------------------------------------ That's great to hear, thanks [~dlee606]. You can follow these instructions to create a pull request on github with your proposed patch: https://community.jboss.org/wiki/GuideToUsePullRequestsWithGitHubAndJIRA > ExtendedDataTable selection with Ctrl+click does not correctly update selection backing bean without clicking first > ------------------------------------------------------------------------------------------------------------------- > > Key: RF-10793 > URL: https://issues.jboss.org/browse/RF-10793 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 3.3.3.Final > Environment: OS: SLES 10 SP2 > JBoss EAP 4.3.0.GA_CP03 > Application using JBoss Seam 2.1.2 > Reporter: Eduard Ereza > Labels: extendedDataTable, richfaces, richfaces-showcase, selection > Fix For: 3.Future > > Attachments: extdt_solution.txt > > > Selecting rows with Ctrl+click on extendedDataTable just after rendering it (first time or reRender) selects them in the backing bean, but then deselecting the same rows with Ctrl+click does not deselect them in the backing bean. The same happens if there is a selection when the component is rendered: then, deselecting a value deselects it from the backing bean, but selecting it again does not select it in the backing bean. > When you click (without Ctrl) for the first time, everything works as it should. > This is also reproduceable on RichFaces Live Demo: http://livedemo.exadel.com/richfaces-demo/richfaces/extendedDataTable.jsf (see Steps to Reproduce). > This is probably related to RF-8681. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-10793) ExtendedDataTable selection with Ctrl+click does not correctly update selection backing bean without clicking first

by David Lee (JIRA)

[ https://issues.jboss.org/browse/RF-10793?page=com.atlassian.jira.plugin.s... ] David Lee commented on RF-10793: -------------------------------- I think I got some idea to fix this bug, but need to modify on TableSelectionRendererContributor.java. Any process I can do to help guys to fix this bug? Like where I can commit that or put the code some where for review? Many thanks > ExtendedDataTable selection with Ctrl+click does not correctly update selection backing bean without clicking first > ------------------------------------------------------------------------------------------------------------------- > > Key: RF-10793 > URL: https://issues.jboss.org/browse/RF-10793 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 3.3.3.Final > Environment: OS: SLES 10 SP2 > JBoss EAP 4.3.0.GA_CP03 > Application using JBoss Seam 2.1.2 > Reporter: Eduard Ereza > Labels: extendedDataTable, richfaces, richfaces-showcase, selection > Fix For: 3.Future > > Attachments: extdt_solution.txt > > > Selecting rows with Ctrl+click on extendedDataTable just after rendering it (first time or reRender) selects them in the backing bean, but then deselecting the same rows with Ctrl+click does not deselect them in the backing bean. The same happens if there is a selection when the component is rendered: then, deselecting a value deselects it from the backing bean, but selecting it again does not select it in the backing bean. > When you click (without Ctrl) for the first time, everything works as it should. > This is also reproduceable on RichFaces Live Demo: http://livedemo.exadel.com/richfaces-demo/richfaces/extendedDataTable.jsf (see Steps to Reproduce). > This is probably related to RF-8681. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-13099) Disabled input text is not visible

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13099?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13099: ------------------------------- Component/s: component-input skinning > Disabled input text is not visible > ---------------------------------- > > Key: RF-13099 > URL: https://issues.jboss.org/browse/RF-13099 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, skinning > Reporter: Kush Kumar > Priority: Minor > Fix For: 4.5.0.Alpha1 > > > Disabled input text is not visible -can you please help me out how can we make it visible or can we change the color of disabled text? -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-13099) Disabled input text is not visible

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13099?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13099: ------------------------------------ In version 4.5.0.Alpha1 we will fix the skin so that you don't need to override it with the mentioned workaround. > Disabled input text is not visible > ---------------------------------- > > Key: RF-13099 > URL: https://issues.jboss.org/browse/RF-13099 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Kush Kumar > Priority: Minor > Fix For: 4.5.0.Alpha1 > > > Disabled input text is not visible -can you please help me out how can we make it visible or can we change the color of disabled text? -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-13099) Disabled input text is not visible

by Kush Kumar (JIRA)

[ https://issues.jboss.org/browse/RF-13099?page=com.atlassian.jira.plugin.s... ] Kush Kumar commented on RF-13099: --------------------------------- Hi Brian , Thank you so much ! You mean version 4.5.0.Alpha1 will not have the same issue what we discussed ? > Disabled input text is not visible > ---------------------------------- > > Key: RF-13099 > URL: https://issues.jboss.org/browse/RF-13099 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Kush Kumar > Priority: Minor > Fix For: 4.5.0.Alpha1 > > > Disabled input text is not visible -can you please help me out how can we make it visible or can we change the color of disabled text? -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-13102) rich:calendar with date pattern- input gets cleared on click

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13102?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-13102. -------------------------------- Resolution: Done Defaulted to the first of the month when the date string has no day value > rich:calendar with date pattern- input gets cleared on click > ------------------------------------------------------------ > > Key: RF-13102 > URL: https://issues.jboss.org/browse/RF-13102 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.2.3.Final, 4.3.2 > Reporter: Jonáš Trantina > Assignee: Brian Leathem > Fix For: 4.3.4 > > > When a rich:calendar component has datePattern without a day (e.g. MM/yyyy) then selected date is cleared when opening the calendar (you can see today date instead of the previously selected date). > However, when the form is sent, the value is correctly assigned to the binded value. > Example: > {noformat} > <rich:calendar value="#{richBean.date}" datePattern="yyyy-MM"/> > {noformat} -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-13087) PopupPanel: button's label is invisible in IE8

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13087?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13087: ------------------------------------ Thanks [~marco-0513], your simple reproduction helped greatly in the resolution of RF-13086. > PopupPanel: button's label is invisible in IE8 > ---------------------------------------------- > > Key: RF-13087 > URL: https://issues.jboss.org/browse/RF-13087 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.2 > Environment: JBoss 6.1, Mojarra 2.1.21 > Reporter: Marco Bulau > Attachments: buttonInPopupPanel.png, JSF2-RichFaces4-PopupPanelIe8Bug.zip, Popup-IE8.png > > > As described by RF-12850, in IE8 the problem still exists that the label/value of a button inside a popup panel (defined as show="true") is not displayed until the mouse move over the button (see screenshot). > Attached you find a simple demo application that demonstrate the problem. -- 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, 8 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 July 2013