July 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13088) Sorting with rich:column doesn't work in Metamer

by Petr Mensik (JIRA)

[ https://issues.jboss.org/browse/RF-13088?page=com.atlassian.jira.plugin.s... ] Petr Mensik updated RF-13088: ----------------------------- Assignee: Brian Leathem (was: Petr Mensik) > Sorting with rich:column doesn't work in Metamer > ------------------------------------------------ > > Key: RF-13088 > URL: https://issues.jboss.org/browse/RF-13088 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.1 > Environment: Fedora 18, Firefox 22 > Reporter: Petr Mensik > Assignee: Brian Leathem > Labels: rich:column > > Sorting doesn't work properly on both Custom Comparator and Sorting page. If you check the ascending or descending radio button, then some sorting is applied to the list but it's definitely not in correct order. It works only if you select unsorted which will sort the list into the ascending order. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13088) Sorting with rich:column doesn't work in Metamer

by Petr Mensik (JIRA)

[ https://issues.jboss.org/browse/RF-13088?page=com.atlassian.jira.plugin.s... ] Petr Mensik commented on RF-13088: ---------------------------------- Nope, behaviour is still the same. > Sorting with rich:column doesn't work in Metamer > ------------------------------------------------ > > Key: RF-13088 > URL: https://issues.jboss.org/browse/RF-13088 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.1 > Environment: Fedora 18, Firefox 22 > Reporter: Petr Mensik > Assignee: Petr Mensik > Labels: rich:column > > Sorting doesn't work properly on both Custom Comparator and Sorting page. If you check the ascending or descending radio button, then some sorting is applied to the list but it's definitely not in correct order. It works only if you select unsorted which will sort the list into the ascending order. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13090) <rich:jQuery> named functions not working as documented

by Vincent Wülcknitz (JIRA)

[ https://issues.jboss.org/browse/RF-13090?page=com.atlassian.jira.plugin.s... ] Vincent Wülcknitz updated RF-13090: ----------------------------------- Git Pull Request: https://github.com/richfaces4/components/pull/81 > <rich:jQuery> named functions not working as documented > ------------------------------------------------------- > > Key: RF-13090 > URL: https://issues.jboss.org/browse/RF-13090 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.3.2 > Reporter: Vincent Wülcknitz > Priority: Minor > Labels: richfaces > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > I have found some strange behaviour with the <rich:jQuery> component when you implement named functions like described in the component reference: > > http://docs.jboss.org/richfaces/latest_4_3_X/Component_Reference/en-US/ht... > > If I implement the given code from the reference: > > # > <h:graphicImage width="50" value="/images/price.png" onmouseover="enlargePic(this, {pwidth:'60px'})" onmouseout="releasePic(this)" /> > <h:graphicImage width="50" value="/images/discount.png" onmouseover="enlargePic(this, {pwidth:'100px'})" onmouseout="releasePic(this)" /> > ... > <rich:jQuery name="enlargePic" query="animate({width:options.pwidth})" /> > <rich:jQuery name="releasePic" query="animate({width:'50px'})"/> > > only the onmouseover calls will work. The prictures will get bigger but not smaller onmouseout. > I found out that if I do some small changes to the onmouseout call it works fine: > > # > <h:graphicImage width="50" value="/images/price.png" onmouseover="enlargePic(this, {pwidth:'60px'})" onmouseout="releasePic(this,{})" /> > <h:graphicImage width="50" value="/images/discount.png" onmouseover="enlargePic(this, {pwidth:'100px'})" onmouseout="releasePic(this,{})" /> > ... > <rich:jQuery name="enlargePic" query="animate({width:options.pwidth})" /> > <rich:jQuery name="releasePic" query="animate({width:'50px'})"/> > It only works when adding a second parameter to the call even if its empty. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13090) <rich:jQuery> named functions not working as documented

by Vincent Wülcknitz (JIRA)

Vincent Wülcknitz created RF-13090: -------------------------------------- Summary: <rich:jQuery> named functions not working as documented Key: RF-13090 URL: https://issues.jboss.org/browse/RF-13090 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-misc Affects Versions: 4.3.2 Reporter: Vincent Wülcknitz Priority: Minor I have found some strange behaviour with the <rich:jQuery> component when you implement named functions like described in the component reference: http://docs.jboss.org/richfaces/latest_4_3_X/Component_Reference/en-US/ht... If I implement the given code from the reference: # <h:graphicImage width="50" value="/images/price.png" onmouseover="enlargePic(this, {pwidth:'60px'})" onmouseout="releasePic(this)" /> <h:graphicImage width="50" value="/images/discount.png" onmouseover="enlargePic(this, {pwidth:'100px'})" onmouseout="releasePic(this)" /> ... <rich:jQuery name="enlargePic" query="animate({width:options.pwidth})" /> <rich:jQuery name="releasePic" query="animate({width:'50px'})"/> only the onmouseover calls will work. The prictures will get bigger but not smaller onmouseout. I found out that if I do some small changes to the onmouseout call it works fine: # <h:graphicImage width="50" value="/images/price.png" onmouseover="enlargePic(this, {pwidth:'60px'})" onmouseout="releasePic(this,{})" /> <h:graphicImage width="50" value="/images/discount.png" onmouseover="enlargePic(this, {pwidth:'100px'})" onmouseout="releasePic(this,{})" /> ... <rich:jQuery name="enlargePic" query="animate({width:options.pwidth})" /> <rich:jQuery name="releasePic" query="animate({width:'50px'})"/> It only works when adding a second parameter to the call even if its empty. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13088) Sorting with rich:column doesn't work in Metamer

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13088?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13088: ------------------------------------ Do you get the behaviour you expect if you set _sortMode="single"_? > Sorting with rich:column doesn't work in Metamer > ------------------------------------------------ > > Key: RF-13088 > URL: https://issues.jboss.org/browse/RF-13088 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.1 > Environment: Fedora 18, Firefox 22 > Reporter: Petr Mensik > Labels: rich:column > > Sorting doesn't work properly on both Custom Comparator and Sorting page. If you check the ascending or descending radio button, then some sorting is applied to the list but it's definitely not in correct order. It works only if you select unsorted which will sort the list into the ascending order. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13088) Sorting with rich:column doesn't work in Metamer

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13088?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13088: ------------------------------- Assignee: Petr Mensik > Sorting with rich:column doesn't work in Metamer > ------------------------------------------------ > > Key: RF-13088 > URL: https://issues.jboss.org/browse/RF-13088 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.1 > Environment: Fedora 18, Firefox 22 > Reporter: Petr Mensik > Assignee: Petr Mensik > Labels: rich:column > > Sorting doesn't work properly on both Custom Comparator and Sorting page. If you check the ascending or descending radio button, then some sorting is applied to the list but it's definitely not in correct order. It works only if you select unsorted which will sort the list into the ascending order. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12273) rich:fileUpload does not work in portlets because it does not utilize javax.faces.encodedURL for the XmlHttpRequest URL

by Ken Finnigan (JIRA)

[ https://issues.jboss.org/browse/RF-12273?page=com.atlassian.jira.plugin.s... ] Ken Finnigan commented on RF-12273: ----------------------------------- Thiers, It's worth ensuring that all the JS files are correctly loaded in the browser. I've personally tested this with a portlet with Portlet Bridge and GateIn, and it works fine. > rich:fileUpload does not work in portlets because it does not utilize javax.faces.encodedURL for the XmlHttpRequest URL > ----------------------------------------------------------------------------------------------------------------------- > > Key: RF-12273 > URL: https://issues.jboss.org/browse/RF-12273 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component, portal > Affects Versions: 4.2.0.Final > Reporter: Neil Griffin > Assignee: Ken Finnigan > Fix For: 4.2.3.CR1, 4.3.0.M2 > > > The fileupload.js JavaScript resource has a bug such that it uses the form's "action" attribute as the XmlHttpRequest URL, rather than the "javax.faces.encodedURL" hidden field value. > I think this is where the problem exists: > {code} __submit: function() { > var originalAction = this.form.attr("action"); > var originalEncoding = this.form.attr("encoding"); > var originalEnctype = this.form.attr("enctype"); > try { > var delimiter = originalAction.indexOf("?") == -1 ? "?" : "&"; > this.form.attr("action", originalAction + delimiter + UID + "=" + this.loadableItem.uid); > this.form.attr("encoding", "multipart/form-data"); > this.form.attr("enctype", "multipart/form-data"); > richfaces.submitForm(this.form, {"org.richfaces.ajax.component": this.id}, this.id); > richfaces.Event.fire(this.element, "onfilesubmit", this.loadableItem.model); > } finally { > this.form.attr("action", originalAction); > this.form.attr("encoding", originalEncoding); > this.form.attr("enctype", originalEnctype); > this.loadableItem.input.removeAttr("name"); > } > },{code} > Until this is fixed, the component will not function in a portlet environment. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12273) rich:fileUpload does not work in portlets because it does not utilize javax.faces.encodedURL for the XmlHttpRequest URL

by Thiers Euller (JIRA)

[ https://issues.jboss.org/browse/RF-12273?page=com.atlassian.jira.plugin.s... ] Thiers Euller edited comment on RF-12273 at 7/11/13 9:47 AM: ------------------------------------------------------------- I'm using version 4.3.2.FINAL and still giving this error. (Just replace the jars to the latest version). I'm forgetting something? {noformat} Uncaught TypeError: Cannot call method 'indexOf' of undefined fileupload.js.jsf:189 $.extend.__submit fileupload.js.jsf:189 jQuery.extend.startUploading fileupload.js.jsf:324 $.extend.__startUpload fileupload.js.jsf:181 proxy jquery.js.jsf:814 jQuery.event.dispatch jquery.js.jsf:3256 elemData.handle.eventHandle {noformat} was (Author: thierseuller): I'm using version 4.3.2.FINAL and still giving this error. (Just replace the jars to the latest version). I'm forgetting something? > rich:fileUpload does not work in portlets because it does not utilize javax.faces.encodedURL for the XmlHttpRequest URL > ----------------------------------------------------------------------------------------------------------------------- > > Key: RF-12273 > URL: https://issues.jboss.org/browse/RF-12273 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component, portal > Affects Versions: 4.2.0.Final > Reporter: Neil Griffin > Assignee: Ken Finnigan > Fix For: 4.2.3.CR1, 4.3.0.M2 > > > The fileupload.js JavaScript resource has a bug such that it uses the form's "action" attribute as the XmlHttpRequest URL, rather than the "javax.faces.encodedURL" hidden field value. > I think this is where the problem exists: > {code} __submit: function() { > var originalAction = this.form.attr("action"); > var originalEncoding = this.form.attr("encoding"); > var originalEnctype = this.form.attr("enctype"); > try { > var delimiter = originalAction.indexOf("?") == -1 ? "?" : "&"; > this.form.attr("action", originalAction + delimiter + UID + "=" + this.loadableItem.uid); > this.form.attr("encoding", "multipart/form-data"); > this.form.attr("enctype", "multipart/form-data"); > richfaces.submitForm(this.form, {"org.richfaces.ajax.component": this.id}, this.id); > richfaces.Event.fire(this.element, "onfilesubmit", this.loadableItem.model); > } finally { > this.form.attr("action", originalAction); > this.form.attr("encoding", originalEncoding); > this.form.attr("enctype", originalEnctype); > this.loadableItem.input.removeAttr("name"); > } > },{code} > Until this is fixed, the component will not function in a portlet environment. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12273) rich:fileUpload does not work in portlets because it does not utilize javax.faces.encodedURL for the XmlHttpRequest URL

by Thiers Euller (JIRA)

[ https://issues.jboss.org/browse/RF-12273?page=com.atlassian.jira.plugin.s... ] Thiers Euller commented on RF-12273: ------------------------------------ I'm using version 4.3.2.FINAL and still giving this error. (Just replace the jars to the latest version). I'm forgetting something? > rich:fileUpload does not work in portlets because it does not utilize javax.faces.encodedURL for the XmlHttpRequest URL > ----------------------------------------------------------------------------------------------------------------------- > > Key: RF-12273 > URL: https://issues.jboss.org/browse/RF-12273 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component, portal > Affects Versions: 4.2.0.Final > Reporter: Neil Griffin > Assignee: Ken Finnigan > Fix For: 4.2.3.CR1, 4.3.0.M2 > > > The fileupload.js JavaScript resource has a bug such that it uses the form's "action" attribute as the XmlHttpRequest URL, rather than the "javax.faces.encodedURL" hidden field value. > I think this is where the problem exists: > {code} __submit: function() { > var originalAction = this.form.attr("action"); > var originalEncoding = this.form.attr("encoding"); > var originalEnctype = this.form.attr("enctype"); > try { > var delimiter = originalAction.indexOf("?") == -1 ? "?" : "&"; > this.form.attr("action", originalAction + delimiter + UID + "=" + this.loadableItem.uid); > this.form.attr("encoding", "multipart/form-data"); > this.form.attr("enctype", "multipart/form-data"); > richfaces.submitForm(this.form, {"org.richfaces.ajax.component": this.id}, this.id); > richfaces.Event.fire(this.element, "onfilesubmit", this.loadableItem.model); > } finally { > this.form.attr("action", originalAction); > this.form.attr("encoding", originalEncoding); > this.form.attr("enctype", originalEnctype); > this.loadableItem.input.removeAttr("name"); > } > },{code} > Until this is fixed, the component will not function in a portlet environment. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-12767) Metamer: rich:collapsibleSubTable don't work with rich:dataScroller

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RF-12767?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on RF-12767: ---------------------------------------------- Boleslaw Dawidowicz <bdawidow(a)redhat.com> changed the Status of [bug 983065|https://bugzilla.redhat.com/show_bug.cgi?id=983065] from NEW to CLOSED > Metamer: rich:collapsibleSubTable don't work with rich:dataScroller > -------------------------------------------------------------------- > > Key: RF-12767 > URL: https://issues.jboss.org/browse/RF-12767 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.2.3.Final > Environment: Ubuntu 12.0.4 LTS, JBoss AS 7.1, Firefox 18.0.1 > Reporter: Petr Mensik > Labels: jboss-as7, portletbridge, richfaces > Fix For: 5-Tracking > > > As title suggested, data scrolling is not working in rich:collapsibleSubTable. You can move to the second page but after that the scroll panel gets frozen and you can move only to first page again. Same thing occurs of you click for example to page 5, you can only move backwards. -- 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, 4 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