[JBoss JIRA] (RF-13177) rich:extendedDataTable scrolling broken on OS-X
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13177?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13177:
-------------------------------
Labels: osx (was: )
> rich:extendedDataTable scrolling broken on OS-X
> -----------------------------------------------
>
> Key: RF-13177
> URL: https://issues.jboss.org/browse/RF-13177
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: base functionality
> Affects Versions: 4.3.3
> Environment: OS-X 10.8.3, Chrome 29.0.1547.62 or Safari or Firefox
> Reporter: Immo Benjes
> Labels: osx
>
> In OS-X scrolling can be done by using two fingers on the touchpad. However this does not work for horizontal scrolling on the rich:extendedDataTable.
> You can scroll vertically but not horizontally.
> The horizontal scrolling with two fingers only works when the mouse is over the actual scrollbar!
> I had a look at the actual html code and it looks like the header, table content and scroller are generated as independent tables. The div that contains the table content (class rf-edt-cnt) has overflow:hidden; set. If you change that to overflow: auto you get the two finger scrolling over the content of the table, however the header and original scrollbar isn't scrolling. Would it be possible to hide the original scroller and synchronize the header (and footer?) when scrolling the content?
> In OS-X you have the option to only show the scrollbar when you scroll. This is quite nice as it gives you a bit more space. However in this case you cannot scroll with the extendedDataTable at all! The scrollbar of the extendedDataTable is hidden in this case and the height/width of the div containing the scrollbar is 0, so you can't navigate over it to enable the scrolling. That basically gives you no way of scrolling!
> See https://community.jboss.org/thread/231502
--
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, 9 months
[JBoss JIRA] (RF-13177) rich:extendedDataTable scrolling broken on OS-X
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13177?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13177:
-------------------------------
Component/s: base functionality
> rich:extendedDataTable scrolling broken on OS-X
> -----------------------------------------------
>
> Key: RF-13177
> URL: https://issues.jboss.org/browse/RF-13177
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: base functionality
> Affects Versions: 4.3.3
> Environment: OS-X 10.8.3, Chrome 29.0.1547.62 or Safari or Firefox
> Reporter: Immo Benjes
>
> In OS-X scrolling can be done by using two fingers on the touchpad. However this does not work for horizontal scrolling on the rich:extendedDataTable.
> You can scroll vertically but not horizontally.
> The horizontal scrolling with two fingers only works when the mouse is over the actual scrollbar!
> I had a look at the actual html code and it looks like the header, table content and scroller are generated as independent tables. The div that contains the table content (class rf-edt-cnt) has overflow:hidden; set. If you change that to overflow: auto you get the two finger scrolling over the content of the table, however the header and original scrollbar isn't scrolling. Would it be possible to hide the original scroller and synchronize the header (and footer?) when scrolling the content?
> In OS-X you have the option to only show the scrollbar when you scroll. This is quite nice as it gives you a bit more space. However in this case you cannot scroll with the extendedDataTable at all! The scrollbar of the extendedDataTable is hidden in this case and the height/width of the div containing the scrollbar is 0, so you can't navigate over it to enable the scrolling. That basically gives you no way of scrolling!
> See https://community.jboss.org/thread/231502
--
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, 9 months
[JBoss JIRA] (RF-13177) rich:extendedDataTable scrolling broken on OS-X
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13177?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13177:
-------------------------------
Fix Version/s: 5-Tracking
> rich:extendedDataTable scrolling broken on OS-X
> -----------------------------------------------
>
> Key: RF-13177
> URL: https://issues.jboss.org/browse/RF-13177
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: base functionality
> Affects Versions: 4.3.3
> Environment: OS-X 10.8.3, Chrome 29.0.1547.62 or Safari or Firefox
> Reporter: Immo Benjes
> Labels: osx
> Fix For: 5-Tracking
>
>
> In OS-X scrolling can be done by using two fingers on the touchpad. However this does not work for horizontal scrolling on the rich:extendedDataTable.
> You can scroll vertically but not horizontally.
> The horizontal scrolling with two fingers only works when the mouse is over the actual scrollbar!
> I had a look at the actual html code and it looks like the header, table content and scroller are generated as independent tables. The div that contains the table content (class rf-edt-cnt) has overflow:hidden; set. If you change that to overflow: auto you get the two finger scrolling over the content of the table, however the header and original scrollbar isn't scrolling. Would it be possible to hide the original scroller and synchronize the header (and footer?) when scrolling the content?
> In OS-X you have the option to only show the scrollbar when you scroll. This is quite nice as it gives you a bit more space. However in this case you cannot scroll with the extendedDataTable at all! The scrollbar of the extendedDataTable is hidden in this case and the height/width of the div containing the scrollbar is 0, so you can't navigate over it to enable the scrolling. That basically gives you no way of scrolling!
> See https://community.jboss.org/thread/231502
--
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, 9 months
[JBoss JIRA] (RF-13177) rich:extendedDataTable scrolling broken on OS-X
by Immo Benjes (JIRA)
[ https://issues.jboss.org/browse/RF-13177?page=com.atlassian.jira.plugin.s... ]
Immo Benjes updated RF-13177:
-----------------------------
Description:
In OS-X scrolling can be done by using two fingers on the touchpad. However this does not work for horizontal scrolling on the rich:extendedDataTable.
You can scroll vertically but not horizontally.
The horizontal scrolling with two fingers only works when the mouse is over the actual scrollbar!
I had a look at the actual html code and it looks like the header, table content and scroller are generated as independent tables. The div that contains the table content (class rf-edt-cnt) has overflow:hidden; set. If you change that to overflow: auto you get the two finger scrolling over the content of the table, however the header and original scrollbar isn't scrolling. Would it be possible to hide the original scroller and synchronize the header (and footer?) when scrolling the content?
In OS-X you have the option to only show the scrollbar when you scroll. This is quite nice as it gives you a bit more space. However in this case you cannot scroll with the extendedDataTable at all! The scrollbar of the extendedDataTable is hidden in this case and the height/width of the div containing the scrollbar is 0, so you can't navigate over it to enable the scrolling. That basically gives you no way of scrolling!
See https://community.jboss.org/thread/231502
was:
In OS-X scrolling can be done by using two fingers on the touchpad. However this does not work for horizontal scrolling on the rich:extendedDataTable.
You can scroll vertically but not horizontally.
The horizontal scrolling with two fingers only works when the mouse is over the actual scrollbar!
I had a look at the actual html code and it looks like the header, table content and scroller are generated as independent tables. The div that contains the table content (class rf-edt-cnt) has overflow:hidden; set. If you change that to overflow: auto you get the two finger scrolling over the content of the table, however the header and original scrollbar isn't scrolling. Would it be possible to hide the original scroller and synchronize the header (and footer?) when scrolling the content?
In OS-X you have the option to only show the scrollbar when you scroll. This is quite nice as it gives you a bit more space. However in this case you cannot scroll with the extendedDataTable at all! The scrollbar of the extendedDataTable is hidden in this case and the height/width of the div containing the scrollbar is 0, so you can't navigate over it to enable the scrolling. That basically gives you no way of scrolling!
> rich:extendedDataTable scrolling broken on OS-X
> -----------------------------------------------
>
> Key: RF-13177
> URL: https://issues.jboss.org/browse/RF-13177
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.3
> Environment: OS-X 10.8.3, Chrome 29.0.1547.62 or Safari or Firefox
> Reporter: Immo Benjes
>
> In OS-X scrolling can be done by using two fingers on the touchpad. However this does not work for horizontal scrolling on the rich:extendedDataTable.
> You can scroll vertically but not horizontally.
> The horizontal scrolling with two fingers only works when the mouse is over the actual scrollbar!
> I had a look at the actual html code and it looks like the header, table content and scroller are generated as independent tables. The div that contains the table content (class rf-edt-cnt) has overflow:hidden; set. If you change that to overflow: auto you get the two finger scrolling over the content of the table, however the header and original scrollbar isn't scrolling. Would it be possible to hide the original scroller and synchronize the header (and footer?) when scrolling the content?
> In OS-X you have the option to only show the scrollbar when you scroll. This is quite nice as it gives you a bit more space. However in this case you cannot scroll with the extendedDataTable at all! The scrollbar of the extendedDataTable is hidden in this case and the height/width of the div containing the scrollbar is 0, so you can't navigate over it to enable the scrolling. That basically gives you no way of scrolling!
> See https://community.jboss.org/thread/231502
--
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, 9 months
[JBoss JIRA] (RF-13177) rich:extendedDataTable scrolling broken on OS-X
by Immo Benjes (JIRA)
Immo Benjes created RF-13177:
--------------------------------
Summary: rich:extendedDataTable scrolling broken on OS-X
Key: RF-13177
URL: https://issues.jboss.org/browse/RF-13177
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.3.3
Environment: OS-X 10.8.3, Chrome 29.0.1547.62 or Safari or Firefox
Reporter: Immo Benjes
In OS-X scrolling can be done by using two fingers on the touchpad. However this does not work for horizontal scrolling on the rich:extendedDataTable.
You can scroll vertically but not horizontally.
The horizontal scrolling with two fingers only works when the mouse is over the actual scrollbar!
I had a look at the actual html code and it looks like the header, table content and scroller are generated as independent tables. The div that contains the table content (class rf-edt-cnt) has overflow:hidden; set. If you change that to overflow: auto you get the two finger scrolling over the content of the table, however the header and original scrollbar isn't scrolling. Would it be possible to hide the original scroller and synchronize the header (and footer?) when scrolling the content?
In OS-X you have the option to only show the scrollbar when you scroll. This is quite nice as it gives you a bit more space. However in this case you cannot scroll with the extendedDataTable at all! The scrollbar of the extendedDataTable is hidden in this case and the height/width of the div containing the scrollbar is 0, so you can't navigate over it to enable the scrolling. That basically gives you no way of scrolling!
--
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, 9 months
[JBoss JIRA] (RF-13176) tree: JS error after selecting an item in tree
by Jiří Štefek (JIRA)
Jiří Štefek created RF-13176:
--------------------------------
Summary: tree: JS error after selecting an item in tree
Key: RF-13176
URL: https://issues.jboss.org/browse/RF-13176
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-tree
Environment: richfaces-5.0.0-SNAPSHOT
FF 18
Tomcat 7.0.32, JBoss AS 7.1
Reporter: Jiří Štefek
Priority: Critical
The selecting of items does not work properly.
After selecting an item (toggling of nodes works fine) from tree a JavaScript error occurs:
{code}
TypeError: RichFaces.$ is not a function
...EventHandler=function(handlerCode){if(handlerCode){return new Function("event",h...
packed.js (line 178)
{code}
This also prevents any further manipulation with tree.
--
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, 9 months
[JBoss JIRA] (RF-12801) org.richfaces.resourceOptimization.enabled parameter with true value disables WebBeansELResolver to register in Websphere
by Sebastian Cramer (JIRA)
[ https://issues.jboss.org/browse/RF-12801?page=com.atlassian.jira.plugin.s... ]
Sebastian Cramer commented on RF-12801:
---------------------------------------
I just started a thread in the forums with some new insight: https://community.jboss.org/message/836710#836710
> org.richfaces.resourceOptimization.enabled parameter with true value disables WebBeansELResolver to register in Websphere
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: RF-12801
> URL: https://issues.jboss.org/browse/RF-12801
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: resource handling
> Affects Versions: 4.3.0.Final
> Environment: Websphere 8.0.0.3 and Websphere 8.0.0.5, Windows 7, Richfaces 4.3.0.Final
> Reporter: Erdem YILMAZ
> Labels: ELResolver, optimization, resource, websphere
>
> when we use context param org.richfaces.resourceOptimization.enabled in web.xml, the CDI listener is not registered in Websphere.
> resourcesOptimization parameter disables org.apache.webbeans.el.WebBeansELResolver in Websphere. In richfaces 4.2.3.Final version, resourceOptimization parameter do not affect the CDI behaviour.
> we have disabled the resource optimization in order to work with richfaces but for the production environment, we prefer to enable it.
--
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, 9 months
[JBoss JIRA] (RF-12802) Move page fragments from repository qa to richfaces5
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-12802?page=com.atlassian.jira.plugin.s... ]
Juraj Húska edited comment on RF-12802 at 9/9/13 5:13 AM:
----------------------------------------------------------
We are still in the process of Page Fragments refactoring, however it is coming to the end.
Following actions need to be done to finish refactoring, so it can be reviewed by you guys:
# finish refactoring of Metamer tests to the new API of: {{r:panelMenu}} and {{r:tree}}
# pair program the most complex refactoring of {{r:calendar}} and refactor tests accordingly
# unify proposed {{Wait}} API for all page fragments
# unify {{AdvancedInteractions}} API for all page fragments
# after review of page fragments from you guys, complete Javadoc
I will cross particular action once it is completed.
was (Author: jhuska):
We are still in the process of Page Fragments refactoring, however it is coming to the end.
Following actions need to be done to finish refactoring, so it can be reviewed by you guys:
* finish refactoring of Metamer tests to the new API of: {{r:panelMenu}} and {{r:tree}}
* pair program the most complex refactoring of {{r:calendar}} and refactor tests accordingly
* unify proposed {{Wait}} API for all page fragments
* unify {{AdvancedInteractions}} API for all page fragments
* after review of page fragments from you guys, complete Javadoc
I will cross particular action once it is completed.
> Move page fragments from repository qa to richfaces5
> ----------------------------------------------------
>
> Key: RF-12802
> URL: https://issues.jboss.org/browse/RF-12802
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Affects Versions: 5.0.0.Alpha1
> Reporter: Pavol Pitonak
> Assignee: Juraj Húska
> Fix For: 5.0.0.Alpha2
>
>
> As discussed on community meeting on Feb 12, we should move page fragments for RichFaces components to richfaces5 repository so that they are distributed with framework.
> We should find out how to prepare them so that they are easy to use for community members. RichFaces QE/dev need to test internals of components, community members will probably test only high-level functionality of components. One possible solution would be to create package "internal" in which there would be page fragments extending those from "public" package. QE team would then use "internal" implementations.
--
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, 9 months