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 10:53:27 GMT


Werner Punz commented on MYFACES-2599:

Ok I can have a look at it on monday (currently busy finalizing the ext-scripting docs) unless
you want to fix it before and I agree this is a bug which prevents frameworks like dojo to
function properly within the bounds of our js (or vice versa is more true),  not sure why
we introduced it firsthand.

> 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