January 2014 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13239) Popup panel: CSS class rf-pp-hdr contains invalid property repeat-x

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13239?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13239: ------------------------------------ [~ppitonak] please verify in RF 4.5 and 5.0 now that the blocking issues have been resolved. > Popup panel: CSS class rf-pp-hdr contains invalid property repeat-x > ------------------------------------------------------------------- > > Key: RF-13239 > URL: https://issues.jboss.org/browse/RF-13239 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 5.0.0.Alpha1 > Environment: RichFaces 5.0.0-SNAPSHOT > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Priority: Minor > Labels: needs-qe > Fix For: 4.3.5, 4.5.0.Alpha2, 5.0.0.Alpha3 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richPopupPanel/simple.xhtml > # check browser console > result: > * Invalid CSS property name: repeat-x (in popupPanel.ecss, line 40) > possible solution: > * replace > {code} > .rf-pp-hdr { > background: url(...); > repeat-x: top left #BED6F8; > ... > } > {code} > * with > {code} > .rf-pp-hdr { > background: url(...) repeat-x top left #BED6F8; > ... > } > {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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13493) Drop down menu rendered on wrong place when page is scrolled

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13493?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13493: ------------------------------------ Works fine for me with Chrome 31.0.1650.63 on Linux. [~ppitonak] can you investigate your failure on Chrome and report back if there are specific versions/OSes that fail? > Drop down menu rendered on wrong place when page is scrolled > ------------------------------------------------------------ > > Key: RF-13493 > URL: https://issues.jboss.org/browse/RF-13493 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 3.3.1.SP4 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Labels: needs-qe > Fix For: 3.3.1.SP4 > > Attachments: dropdownmenu.png > > > # build RichFaces demo from branch https://svn.jboss.org/repos/richfaces/branches/enterprise/3.3.1.SP4/sampl... > # deploy to EAP 5.2 > # open page http://localhost:8080/richfaces-demo/richfaces/dropDownMenu.jsf?c=dropDow... > # open drop down menu (correct) > # scroll down the page and open drop down menu again > result: > * menu is rendered on wrong place (higher than expected) > * the more you scroll the page, the further it appears > * see attached screenshot > * reproducible in IE7, IE8 and Chrome 32 -- 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-11973) rich:contextMenu - after ajax re-render of table contextMenu no longer works

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-11973?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-11973. -------------------------------- Resolution: Done Fixed in 5 > rich:contextMenu - after ajax re-render of table contextMenu no longer works > ---------------------------------------------------------------------------- > > Key: RF-11973 > URL: https://issues.jboss.org/browse/RF-11973 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.2.0.CR1, 4.3.2 > Environment: chrome browser / glassfish 3.1.1 / mojarra 2.1.6 > Reporter: Brendan Healey > Assignee: Brian Leathem > Fix For: 4.3.5, 4.5.0.Alpha2, 5.0.0.Alpha3 > > > With the following code structure, when the page is first rendered > you can right click on a row in the table and the context menu appears. > After pushing the commandButton subsequent right clicks show the > default browser right click menu, and not the context menu. > {code} > <rich:extendedDataTable id="mytable"> > ... > </rich:extendedDataTable> > <a4j:commandButton value="push" render="mytable"/> > <rich:contextMenu target="mytable" mode="ajax"> > <rich:menuItem label="Delete" > mode="ajax" > onclick="alert('hello, world!')"/> > </rich:contextMenu> > {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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13488) Photoalbum: facebook login - User cancelled login or did not fully authorize.

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13488?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13488: ------------------------------------ [~michpetrov] are you saying you are unable to reproduce this issue? > Photoalbum: facebook login - User cancelled login or did not fully authorize. > ----------------------------------------------------------------------------- > > Key: RF-13488 > URL: https://issues.jboss.org/browse/RF-13488 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.3.5 > Environment: Chrome 31, Firefox 26 > JBoss EAP 6.1.1.GA > Reporter: Lukáš Fryč > Assignee: Michal Petrov > Labels: photoalbum > Attachments: screenshot01.png > > > Steps to reproduce: > 1. without being logged into Facebook account > 2. open Photoalbum app: http://localhost:8080/richfaces-photoalbum/ > 3. click Login > 4. click Facebook logo to log into > 5. type the Facebook credentials > FAIL: following error appears: > {code} > User cancelled login or did not fully authorize > {code} > (Note: I had to disable popup blocking for that page, but it doesn't work though. I repeated steps above after disabling popups.) > I can see no errors in browser console or server console. -- 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-13503) Richfaces 3.3.3-final conflict jquery+bootstrap

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13503?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13503: ------------------------------- Fix Version/s: 3.Future > Richfaces 3.3.3-final conflict jquery+bootstrap > ----------------------------------------------- > > Key: RF-13503 > URL: https://issues.jboss.org/browse/RF-13503 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Marcius Brandao > Fix For: 3.Future > > > we implement the bootstrap: > in web.xml : org.richfaces.SKIN=plain > and no xhtml: > <head> > <link rel="stylesheet" href="//netdna.bootstrapcdn.com/bootstrap/3.0.3/css/bootstrap.min.css"/> > </head> > <body> > <rich:toolBar>...</<rich:toolBar> > <nav class="navbar navbar-default" role="navigation"> > <ul class="nav navbar-nav navbar-right"> > <li class="dropdown"> > <a href="#" class="dropdown-toggle" data-toggle="dropdown">Dropdown <b class="caret"></b></a> > <ul class="dropdown-menu"> > <li><a href="#">Action</a></li> > <li><a href="#">Another action</a></li> > <li><a href="#">Something else here</a></li> > <li class="divider"></li> > <li><a href="#">Separated link</a></li> > </ul> > </li> > </ul> > </div> > </nav> > <script src="http://code.jquery.com/jquery.js"/> > <script src="//netdna.bootstrapcdn.com/bootstrap/3.0.3/js/bootstrap.min.js"/> > <script type="text/javascript"> > jQuery.noConflict(); > </script> > </body> > then skin work, but, only the "rich controls" work. -- 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-13504) ExtendedPartialViewContext should write ClientWindow ID updates to the partial response

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13504?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13504: ------------------------------- Summary: ExtendedPartialViewContext should write ClientWindow ID updates to the partial response (was: ExtendedPartialViewContext should write ClientWindow ID updates to a partial response) > ExtendedPartialViewContext should write ClientWindow ID updates to the partial response > --------------------------------------------------------------------------------------- > > Key: RF-13504 > URL: https://issues.jboss.org/browse/RF-13504 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 5.0.0.Alpha2 > Reporter: Lukáš Fryč > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > > During code inspection for RF-13317 I have noticed [we are not writing client-window ID|https://github.com/richfaces/richfaces/blob/2d6e657136e409f67d837a7a30...] into the response as [Mojarra does|https://github.com/jboss/mojarra/blob/2.2.4-jbossorg-1/jsf-ri/src/ma...]. > Framework tests are needed to cover this issue. -- 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-13317) ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate()

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13317?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13317: ------------------------------------ Let's let it stabilize in the 5 branch and back port it as appropriate. Maybe schedule a jira for 4.3.6 to address the backport. > ExtendedPartialViewContextImpl should specify correct javax.faces.ViewState id in startUpdate() > ----------------------------------------------------------------------------------------------- > > Key: RF-13317 > URL: https://issues.jboss.org/browse/RF-13317 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Environment: Wildfly-8.0.0.Beta1, jsf-impl-2.2.3-jbossorg-1 > Reporter: Matti Bickel > Assignee: Lukáš Fryč > Priority: Critical > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > > I'm using several {{<rich:autocomplete>}} fields in a {{<h:form>}}, but have noticed the issue with several other AJAX requests: > When the response comes back, the data is fine but I get a JSF error saying > bq. During update: javax.faces.ViewState not found > Following that, no componentData is available to the Autocomplete component and no suggestions get displayed. > For reference the [javadoc for ResponseStateManager.VIEW_STATE_PARAM|https://javaserverfaces.java.net/no...] says: > {quote} > Implementations must use this constant field value as the name of the client parameter in which to save the state between requests. The id attribute must be a concatenation of the return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant field value, the separator char, and a number that is guaranteed to be unique with respect to all the other instances of this kind of client parameter in the view. > {quote} -- 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-13506) Incorrect information on showcase fileUpload sample page (maxRequestSize description)

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13506?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13506: ------------------------------- Fix Version/s: 4.3.6 (was: 4.3.5) > Incorrect information on showcase fileUpload sample page (maxRequestSize description) > ------------------------------------------------------------------------------------- > > Key: RF-13506 > URL: https://issues.jboss.org/browse/RF-13506 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-input, examples, showcase > Affects Versions: 4.3.4 > Reporter: Vasil Lukach > Priority: Trivial > Fix For: 4.3.6 > > > http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=fileUpload page contains incorrect information: > "maxRequestSize attribute defines max size in bytes of the uploaded files (1000000 for this example)". > But based on "This example allows you to upload up to 5 files. The file extension is limited to GIF, JPG, BMP, PNG and the maximum size of each file must not exceed 100kB" number 1000000 should be changed to 102400. -- 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-13506) Incorrect information on showcase fileUpload sample page (maxRequestSize description)

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13506?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13506: ------------------------------- Fix Version/s: 4.3.5 > Incorrect information on showcase fileUpload sample page (maxRequestSize description) > ------------------------------------------------------------------------------------- > > Key: RF-13506 > URL: https://issues.jboss.org/browse/RF-13506 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-input, examples, showcase > Affects Versions: 4.3.4 > Reporter: Vasil Lukach > Priority: Trivial > Fix For: 4.3.5 > > > http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=fileUpload page contains incorrect information: > "maxRequestSize attribute defines max size in bytes of the uploaded files (1000000 for this example)". > But based on "This example allows you to upload up to 5 files. The file extension is limited to GIF, JPG, BMP, PNG and the maximum size of each file must not exceed 100kB" number 1000000 should be changed to 102400. -- 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-13506) Incorrect information on showcase fileUpload sample page (maxRequestSize description)

by Vasil Lukach (JIRA)

Vasil Lukach created RF-13506: --------------------------------- Summary: Incorrect information on showcase fileUpload sample page (maxRequestSize description) Key: RF-13506 URL: https://issues.jboss.org/browse/RF-13506 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component-input, examples, showcase Affects Versions: 4.3.4 Reporter: Vasil Lukach Priority: Trivial http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=fileUpload page contains incorrect information: "maxRequestSize attribute defines max size in bytes of the uploaded files (1000000 for this example)". But based on "This example allows you to upload up to 5 files. The file extension is limited to GIF, JPG, BMP, PNG and the maximum size of each file must not exceed 100kB" number 1000000 should be changed to 102400. -- 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 January 2014