[JBoss JIRA] Created: (RF-10994) DnD: scripts not getting loaded via ajax
by Ilya Shaikovsky (JIRA)
DnD: scripts not getting loaded via ajax
----------------------------------------
Key: RF-10994
URL: https://issues.jboss.org/browse/RF-10994
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-drag/drop
Affects Versions: 4.0.0.Final
Reporter: Ilya Shaikovsky
<rich:tree value="#{aaa.rootNode}" nodeType="#{node.type}"
var="node">
<rich:treeNode type="t1">
<a4j:outputPanel layout="block">
<rich:dropTarget acceptedTypes="file"
dropListener="#{aaa.process}" />
<h:outputText value="#{node.label}" />
</a4j:outputPanel>
</rich:treeNode>
<rich:treeNode type="t2">
<a4j:outputPanel layout="block">
<rich:dragSource type="file" />
<h:outputText value="#{node.label}" />
</a4j:outputPanel>
</rich:treeNode>
</rich:tree>
Tree by default using ajax mode. So when you expanding nodes -leafs which getting loaded should be draggable. But there is no draggable script resource so you could see JS errors instead saying that Draggable si not a constructor.
If change toggleType to client - works fine. If add any draggable component to the page - it also starts works as scripts already inplace.
(should be easier to reproduce with tab panel or just conditionally rendered panel for example).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] Created: (RF-10947) rich:dragSource doesn't work after being rerendered via ajax
by Adrian Meredith (JIRA)
rich:dragSource doesn't work after being rerendered via ajax
------------------------------------------------------------
Key: RF-10947
URL: https://issues.jboss.org/browse/RF-10947
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-drag/drop
Affects Versions: 4.0.0.Final
Environment: mojarra 2.1.1 gf3.1
Reporter: Adrian Meredith
Drag Source is not applied
using the following code in a composite component
{code}
<a4j:outputPanel layout="block" styleClass="rf-ind-drag" >
<rich:dragSource type="webResult" dragValue="1"/>
<h:outputText value="works"></h:outputText>
</a4j:outputPanel>
<h:panelGroup id="content" layout="block" rendered="#{cc.attrs.rendered}" style="width: 100%; height:100%;">
<a4j:outputPanel layout="block" styleClass="rf-ind-drag" >
<rich:dragSource type="webResult" dragValue="1"/>
<h:outputText value="doesn't work"></h:outputText>
</a4j:outputPanel>
...
{code}
Basically the panel at the top is draggable, the one at the bottom (which is below the panelGroup) is not. Looking at the source its as though dragSource isn't even there as it is rendered without any reference to it (i.e. no ui-draggable class for example).
Drag and drop support was the main reason i'm using richfaces! so its very important to me as i one to drag rows from our table widget onto another panel for quick tagging of results. Unfortunately I'm gonna be away for the next two weeks but It'd be good to get more information on it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] Created: (RF-11343) tooltip: does not work attached to parent input
by Dmitry Volkov (JIRA)
tooltip: does not work attached to parent input
-----------------------------------------------
Key: RF-11343
URL: https://issues.jboss.org/browse/RF-11343
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-output
Affects Versions: 4.0.0.Final
Environment: Firefox 6, IE 8, MyFaces 2.0.3, Websphere AS 8
Reporter: Dmitry Volkov
Tooltip does not work:
{code:xml}
<h:form>
<a4j:outputPanel id="pn">
<h:inputText>
<rich:tooltip>
Hello world!
</rich:tooltip>
</h:inputText>
<a4j:commandButton value="rerender" render="pn"/>
</a4j:outputPanel>
</h:form>
{code}
But works after ajax rerender("rerender" button click).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] Created: (RF-1107) Scrollable dataTable. Header scrolled badly on TAB button.
by Ilya Shaikovsky (JIRA)
Scrollable dataTable. Header scrolled badly on TAB button.
----------------------------------------------------------
Key: RF-1107
URL: http://jira.jboss.com/jira/browse/RF-1107
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.0
Environment: FF 2.0.0.6
Reporter: Ilya Shaikovsky
Assigned To: Konstantin Mishin
Fix For: 3.2.0
Two use-cases failed:
"case - 1.png"
frozenColCount=0
all the columns with inputs
last columns aren't in visible part
When I use TAB key - columns scrolled to be displayed (good) but headers jsut stays (Wrong!)
"case - 2.png"
frozenColCount=2
all the columns with inputs
last columns aren't in visible part
I use TAB key. Focused inputs changed one by one only in "frozen zone" (seems good), but after I press TAB on the last input - the focus jumps to non frozen column input and frozen columns - scrolled and shifted down(Wrong!). But headers still aren't scrolled (good in this case).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] Created: (RF-10569) MyFaces 2.0.X on Tomcat 7 does not property inject managed properties prior to calling @PostConstruct on Beans
by Jay Balunas (JIRA)
MyFaces 2.0.X on Tomcat 7 does not property inject managed properties prior to calling @PostConstruct on Beans
--------------------------------------------------------------------------------------------------------------
Key: RF-10569
URL: https://issues.jboss.org/browse/RF-10569
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: third-party
Affects Versions: 4.0.0.Milestone6
Environment: MyFaces 2.0.X
Tomcat 7
Reporter: Jay Balunas
Assignee: Jay Balunas
Fix For: 4.0.0.CR1
See https://issues.apache.org/jira/browse/MYFACES-3035 to details.
We have several jira's that are all traced back to this issue, and there seems not quick workaround. We are following the issue, and discussing with MyFaces team.
For now please be very conscious of this when testing MyFaces on Tomcat 7. If you believe an issue could be related to this please ask or investigate so we don't get overloaded with jiras related to this.
Note that to see these issues with the richfaces showcase you must turn on extra logging via the logging.properties file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] Created: (RF-11004) Slider: JavaScript error with f:ajax
by Pavol Pitonak (JIRA)
Slider: JavaScript error with f:ajax
------------------------------------
Key: RF-11004
URL: https://issues.jboss.org/browse/RF-11004
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-input
Affects Versions: 4.0.0.Final
Environment: RichFaces 4.1.0-SNAPSHOT
Metamer 4.1.0-SNAPSHOT r.22511
Mojarra 2.0.3-b05
JBoss AS 6.0.0.Final
OpenJDK Runtime Environment 1.6.0_20-b20 @ Linux
Chrome 11.0.696.71 @ Linux i686
Reporter: Pavol Pitonak
# deploy Metamer and open http://localhost:8080/metamer/faces/components/richInputNumberSlider/fAja...
# slide on slider
result:
*Uncaught ReferenceError: mojarra is not defined* fAjax.xhtml:668
*RichFaces.ui.InputNumberSlider.onchange* fAjax.xhtml:668
*richfaces.ui.InputNumberSlider.richfaces.BaseComponent.extendClass.__setValue* inputNumberSlider.js:112
*richfaces.ui.InputNumberSlider.richfaces.BaseComponent.extendClass.__mousemoveHandler* inputNumberSlider.js:192
*richfaces.ui.InputNumberSlider.richfaces.BaseComponent.extendClass.__mousedownHandler* inputNumberSlider.js:179
*jQuery.jQuery.extend.proxy.proxy* jquery.js:768
*jQuery.event.handle* jquery.js:2562
*jQuery.event.add.elemData.handle.eventHandle* jquery.js:2201
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months