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 14:45:27 GMT


Werner Punz commented on MYFACES-2599:

The biggest issue I see is, the name gets posted so that is a non issue, but the item is detached,
so you cannot really determine the parent form anymore unless we have a single one. I can
add another fallback which tries to pickup elements with the same name as the original one
if the name is set, this hopefully fixes the problem to some degree, but not in 100% of all
cases of multiple forms.

> 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