myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Werner Punz (JIRA)" <>
Subject [jira] Commented: (MYFACES-2599) ajax javascript checks for existence of triggering html element
Date Fri, 12 Mar 2010 15:03:27 GMT


Werner Punz commented on MYFACES-2599:

ok additional comment, I have also coded some fuzzy form detection which should help further
to pick the correct form up in such a detachement case, but I think the best solution to this
problem is on the users side.
I would recommend to simply use the manual javascript ajax trigger in this case and use the
parent form or some hidden control as origin of all things (aka source parameter), you still
can drag in your controls id over the execute parameters.

> ajax javascript checks for existence of triggering html element
> ---------------------------------------------------------------
>                 Key: MYFACES-2599
>                 URL:
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: JSR-314
>    Affects Versions: 2.0.0-beta-2
>         Environment: Javascript
>            Reporter: Ganesh Jung
> This one is a bit special. I remove the triggering element from the DOM, afterwards I
trigger it's onchange method. Works with Mojarra, but MyFaces insists, that the triggering
element must exist in the DOM, though this isn't necessary from the spec.
> 		<h:form id="testForm">
> 	 		<h:inputText id="test" value="#{myBean.test}" >
> 				<f:ajax render="test2"/>
> 	    	</h:inputText>
> 			<h:inputText id="test2" value="#{myBean.test}" />
> 		    <script type="text/javascript">
> 				//<![CDATA[
> 	    		var myTest = document.getElementById("testForm:test");
> 	    		var test_onchange = myTest.onchange;
> 	    		myTest.parentNode.removeChild(myTest);
> 	    		test_onchange();
> 				//]]>
> 			</script>
> 		</h:form>

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message