April 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12820) AutoComplete Layout Table is broken

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12820?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12820: ------------------------------- Fix Version/s: 5-Tracking > AutoComplete Layout Table is broken > ----------------------------------- > > Key: RF-12820 > URL: https://issues.jboss.org/browse/RF-12820 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.Final, 4.2.3.Final, 4.3.0.Final > Reporter: nathan dennis > Assignee: Brian Leathem > Labels: rich:autocomplete, testcase_provided > Fix For: 5-Tracking > > > if the parameter layout="table" is passed, the component behaves with undocumented features. > When typing in the input a selection list is displayed. Mouse over the selection list and the wrong selection is displayed in the input. > This problem can be recreated in the show case by simply added the layout=”table” parameter to and existing autocomplete component. > Though in the showcase there is limited selections, if a larger listed is added you can see that the first highlighted row maps to the correct selection +1... the second highlighted row maps to the correct selection to +2 ..etc.. so it appears there is an iterator off somewhere. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12820) AutoComplete Layout Table is broken

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12820?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12820: ------------------------------- Labels: rich:autocomplete testcase_provided (was: rich:autocomplete) > AutoComplete Layout Table is broken > ----------------------------------- > > Key: RF-12820 > URL: https://issues.jboss.org/browse/RF-12820 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.Final, 4.2.3.Final, 4.3.0.Final > Reporter: nathan dennis > Assignee: Brian Leathem > Labels: rich:autocomplete, testcase_provided > > if the parameter layout="table" is passed, the component behaves with undocumented features. > When typing in the input a selection list is displayed. Mouse over the selection list and the wrong selection is displayed in the input. > This problem can be recreated in the show case by simply added the layout=”table” parameter to and existing autocomplete component. > Though in the showcase there is limited selections, if a larger listed is added you can see that the first highlighted row maps to the correct selection +1... the second highlighted row maps to the correct selection to +2 ..etc.. so it appears there is an iterator off somewhere. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12873) I am using <a4j:mediaoutput> to display multiple charts. some times charts are not displayed(rendered) properly.

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12873?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-12873. -------------------------------- Labels: (was: waiting_on_user) Resolution: Incomplete Description > I am using <a4j:mediaoutput> to display multiple charts. some times charts are not displayed(rendered) properly. > ---------------------------------------------------------------------------------------------------------------- > > Key: RF-12873 > URL: https://issues.jboss.org/browse/RF-12873 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: vinay m > -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12836) Component control doesn't work when a button is disabled

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12836?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-12836. -------------------------------- Labels: (was: waiting_on_user) Resolution: Won't Fix > Component control doesn't work when a button is disabled > -------------------------------------------------------- > > Key: RF-12836 > URL: https://issues.jboss.org/browse/RF-12836 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.0.Final > Reporter: Migore S > > I'm trying to add a rich:componentControl to show a popup when a butotn is clicked, but when the button is disabled it doesn't work. > {code} > <h:commandButton id="delete-all-button" value="#{msgs.geral_excluir_selecionados}" > rendered="#{bean.dataModel.rowCount != 0}" > type="button" disabled="true"> > <rich:componentControl event="click" target="confirm-popup" operation="show"> > <a4j:param noEscape="true" value="event" /> > <rich:hashParam> > <f:param name="width" value="500" /> > <f:param name="height" value="300" /> > <f:param name="minWidth" value="300" /> > <f:param name="minHeight" value="150" /> > <a4j:param noEscape="true" name="left" value="(jQuery(window).width()/2)-250" /> > <a4j:param noEscape="true" name="top" value="(jQuery(window).height()/2)-150" /> > </rich:hashParam> > </rich:componentControl> > </h:commandButton> > {code} > If I remove the disabled attribute it works. > Issue on the forum: https://community.jboss.org/thread/222320 -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12898) Tie RichFaces 4.3 to CDK 4.3.1.Final

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12898?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12898: ------------------------------- Original Estimate: 15 minutes Remaining Estimate: 15 minutes > Tie RichFaces 4.3 to CDK 4.3.1.Final > ------------------------------------ > > Key: RF-12898 > URL: https://issues.jboss.org/browse/RF-12898 > Project: RichFaces > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.3.2 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > The RichFaces CDK master is now 4.5.x development. > We need to stop using the master for a full build > and tie the framework build to latest released CDK: 4.3.1.Final. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12849) Showcase - update readme - remove obsolete, add new

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12849?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12849: ------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > Showcase - update readme - remove obsolete, add new > --------------------------------------------------- > > Key: RF-12849 > URL: https://issues.jboss.org/browse/RF-12849 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: doc, showcase > Affects Versions: 4.3.1 > Reporter: Juraj Húska > Assignee: Juraj Húska > Fix For: 4.3.2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > After rewriting showcase readme to markdown syntax I would update it for example with following: > * reference to showcase online demo > * remove publishing to GAE and put there publishing to Openshift instead > * I would create small clickable TOC in the top of the page > * remove deploying on JBoss AS 6 and maybe add deploying on EAP 6 (it is now available to download) > * Mention JBDS as an option -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12850) Popup panel: button's label is invisible in IE10

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12850?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12850: ------------------------------- Original Estimate: 3 hours Remaining Estimate: 3 hours > Popup panel: button's label is invisible in IE10 > ------------------------------------------------ > > Key: RF-12850 > URL: https://issues.jboss.org/browse/RF-12850 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.2.3.Final, 4.3.0.Final, 4.3.1 > Environment: RichFaces 4.3.2-SNAPSHOT > EAP 6.0.1, Tomcat 6.0.32, Tomcat 7.0.35 > Mojarra 2.1.7, 2.1.17, MyFaces 2.1.10 > Internet Explorer 9, 10 > Reporter: Pavol Pitonak > Fix For: 4.3.2 > > Attachments: buttonInPopupPanel.png > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > {code:xml} > <rich:popupPanel id="panel" show="true" header="xxx"> > <h:commandButton id="button" value="Submit" /> > </rich:popupPanel> > {code} > If a page with code snippet above is opened in IE9/IE10, the label "Submit" of button is not displayed until mouse over event. > Since it appears in all JSF implementations and on all runtime containers and works in browsers different from IE, it looks like a bug in IE interpretation of CSS classes. > Sample works fine when header of popup panel is not displayed (i.e. header attribute isn't set and no facet is defined). -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12839) Toggle panels: ajax-related attributes don't work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12839?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12839: ------------------------------- Original Estimate: 2 hours Remaining Estimate: 2 hours > Toggle panels: ajax-related attributes don't work > ------------------------------------------------- > > Key: RF-12839 > URL: https://issues.jboss.org/browse/RF-12839 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.3.1 > Environment: RichFaces 4.3.2-SNAPSHOT > Metamer 4.3.2-SNAPSHOT > JBoss Application Server: Weld Integration 7.1.3.Final-redhat-4 > JBoss AS 7.1.3.Final-redhat-4 > Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux > Chrome 25.0.1364.160 @ Linux x86_64 > Reporter: Pavol Pitonak > Labels: regression > Fix For: 4.3.2 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTab/simple.xhtml > # set oncomplete to "alert('complete')" > # switch to tab 2 and back to tab 1 > result: > * alert should be diplayed but isn't > * tabs are correctly switched > * worked fine in 4.2.3.Final > * several attributes don't work - onbegin, onbeforedomupdate, oncomplete, data, execute, immediate, render, limitRender, status > * affected components: tab, toggle panel item, accordion item -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12843) Apply unix style line-endings to the entire codebase

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12843?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12843: ------------------------------- Original Estimate: 30 minutes Remaining Estimate: 30 minutes > Apply unix style line-endings to the entire codebase > ---------------------------------------------------- > > Key: RF-12843 > URL: https://issues.jboss.org/browse/RF-12843 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: clean-up > Reporter: Brian Leathem > Fix For: 4.3.2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Having only unix-style line-endings in place will ease the backporting of issues from RichFaces 5. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-12848) Error "source is not defined" after richfaces-jsf-event.js merge

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12848?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12848: ------------------------------- Original Estimate: 2 hours Remaining Estimate: 2 hours > Error "source is not defined" after richfaces-jsf-event.js merge > ---------------------------------------------------------------- > > Key: RF-12848 > URL: https://issues.jboss.org/browse/RF-12848 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.3.1 > Reporter: Torben Greiser > Priority: Critical > Labels: regression > Fix For: 4.3.2, 5-Tracking > > Attachments: rf12848_1.xhtml > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Commit 9255380d626227d909bbcd59ea3bc604966ea5bb breaks the following jsf.ajax.request: > {code} > jsf.ajax.request("MyContainer:MySelectionForm", "valueChange", {}); > {code} > In <a4j:log/> the following error is displayed: > {code} > richfaces.queue: ajax submit error: source is not defined > {code} > After inspecting richfaces.js I located the cause of the error: > {code} > var getFormElement = function(sourceElement) { > if ($(sourceElement).is('form')) { > return source; > } else { > return $('form').has(sourceElement).get(0); > } > }; > {code} > First if-statement evaluates to true, returning source, which itself is not defined: > {code} > ReferenceError: source is not defined > {code} -- 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

12 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues April 2013