December 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13413) orderingList, pickList: the buttons have different size on IE

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13413?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13413: ------------------------------------ In [richwidgets/issues/53|https://github.com/richwidgets/richwidgets/issues/53] this was fixed for FireFox by using the CSS 3 flexbox technique. According to this [w3c schools page|http://www.w3schools.com/cssref/css3_pr_box-flex.asp] css3 flexbox is only supported in ie >= 10, but we have to sue the {{-ms-flex}} property. I've filed a new richwidget issue to track this: https://github.com/richwidgets/richwidgets/issues/159 > orderingList, pickList: the buttons have different size on IE > ------------------------------------------------------------- > > Key: RF-13413 > URL: https://issues.jboss.org/browse/RF-13413 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Environment: IE 9, IE 10 > Reporter: Jiří Štefek > Attachments: 1.png, 2.png > > > In both layouts -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13412) autocomplete: after item selection the input is re-focused on IE

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13412?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13412: ------------------------------------ [~jstefek] is this reproducible in a RichWidgets sample? > autocomplete: after item selection the input is re-focused on IE > ---------------------------------------------------------------- > > Key: RF-13412 > URL: https://issues.jboss.org/browse/RF-13412 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha2 > Environment: IE 9, IE 10 > Reporter: Jiří Štefek > Fix For: 5.0.0.Alpha3 > > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13412) autocomplete: after item selection the input is re-focused on IE

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13412?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13412: ------------------------------- Fix Version/s: 5.0.0.Alpha3 > autocomplete: after item selection the input is re-focused on IE > ---------------------------------------------------------------- > > Key: RF-13412 > URL: https://issues.jboss.org/browse/RF-13412 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 5.0.0.Alpha2 > Environment: IE 9, IE 10 > Reporter: Jiří Štefek > Fix For: 5.0.0.Alpha3 > > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13410) Inplace components (select, input): when triggering 'click' event on control buttons a wrong request is made

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13410?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13410: ------------------------------- Fix Version/s: 4.5-Tracking > Inplace components (select, input): when triggering 'click' event on control buttons a wrong request is made > ------------------------------------------------------------------------------------------------------------ > > Key: RF-13410 > URL: https://issues.jboss.org/browse/RF-13410 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4, 5.0.0.Alpha1 > Reporter: Jiří Štefek > Fix For: 4.5-Tracking > > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richInplaceInput/simple.xhtml > # set @showControls=true > # open console and run this command: > {code}$("[id='form:inplaceInputCancelbtn']").trigger('click');{code} > * have: an HTTP request is sent > * expected: no request is sent (canceling the value, when confirming an ajax request should be made) > With this command it works as expected: > {code}$("[id='form:inplaceInputCancelbtn']").trigger('mousedown');{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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13410) Inplace components (select, input): when triggering 'click' event on control buttons a wrong request is made

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13410?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13410: ------------------------------- Fix Version/s: 5-Tracking (was: 4.5-Tracking) > Inplace components (select, input): when triggering 'click' event on control buttons a wrong request is made > ------------------------------------------------------------------------------------------------------------ > > Key: RF-13410 > URL: https://issues.jboss.org/browse/RF-13410 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4, 5.0.0.Alpha1 > Reporter: Jiří Štefek > Fix For: 5-Tracking > > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richInplaceInput/simple.xhtml > # set @showControls=true > # open console and run this command: > {code}$("[id='form:inplaceInputCancelbtn']").trigger('click');{code} > * have: an HTTP request is sent > * expected: no request is sent (canceling the value, when confirming an ajax request should be made) > With this command it works as expected: > {code}$("[id='form:inplaceInputCancelbtn']").trigger('mousedown');{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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13408) ExtendedDataTable, ajax loading delay of 1000ms

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13408?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13408: ------------------------------------ Nice idea. We'll file this feature request away for future consideration. If you would like to accelerate it's implementation, feel free to file a Pull Request. > ExtendedDataTable, ajax loading delay of 1000ms > ----------------------------------------------- > > Key: RF-13408 > URL: https://issues.jboss.org/browse/RF-13408 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: Holger Walter > Fix For: 5-Tracking > > > When using ajax loading in the extendeddatatable, an ajax data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy. > I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js , bodyscrollListener) > Is it possible to reduce this timeout, or make it configurable via properties -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13408) ExtendedDataTable, ajax loading delay of 1000ms

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13408?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13408: ------------------------------- Issue Type: Feature Request (was: Enhancement) > ExtendedDataTable, ajax loading delay of 1000ms > ----------------------------------------------- > > Key: RF-13408 > URL: https://issues.jboss.org/browse/RF-13408 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: Holger Walter > > When using ajax loading in the extendeddatatable, an ajax data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy. > I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js , bodyscrollListener) > Is it possible to reduce this timeout, or make it configurable via properties -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13408) ExtendedDataTable, ajax loading delay of 1000ms

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13408?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13408: ------------------------------- Fix Version/s: 5-Tracking > ExtendedDataTable, ajax loading delay of 1000ms > ----------------------------------------------- > > Key: RF-13408 > URL: https://issues.jboss.org/browse/RF-13408 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Reporter: Holger Walter > Fix For: 5-Tracking > > > When using ajax loading in the extendeddatatable, an ajax data load is triggered when scrolling down to the end of the table. However, this data loadig action is delayed by 1000ms, which gives the user the feeling that the application is quite laggy. > I've taken a look at the javascript code of the extendeddatatable, and saw that the 1000ms delay is hard coded. (extendeddatatable.js , bodyscrollListener) > Is it possible to reduce this timeout, or make it configurable via properties -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13404) Port the RichFaces 5 improvements back to RichFaces 4.3

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13404?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13404: ------------------------------------ Nice work, thanks [~mpetrov]! > Port the RichFaces 5 improvements back to RichFaces 4.3 > ------------------------------------------------------- > > Key: RF-13404 > URL: https://issues.jboss.org/browse/RF-13404 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: examples > Reporter: Brian Leathem > Assignee: Michal Petrov > Fix For: 4.3.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, 4 months

1
0
0 / 0

[JBoss JIRA] (RF-13400) PickList from Metamer is not responsive on real mobile device

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13400?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13400: ------------------------------------ I'll have to take a look. Can you provide steps to reproduce? > PickList from Metamer is not responsive on real mobile device > ------------------------------------------------------------- > > Key: RF-13400 > URL: https://issues.jboss.org/browse/RF-13400 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Reporter: Juraj Húska > Priority: Critical > > PickList in the _Metamer_ demo is not responsive at all on real mobile device. > When changing the size of the desktop browser screen it works correctly. > Note that RichWidgets are responsive correctly on mobile devices. -- 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, 4 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 December 2013