You are viewing a plain text version of this content. The canonical link for it is here.

Posted to xap-commits@incubator.apache.org by jm...@apache.org on 2007/06/12 22:04:31 UTC

svn commit: r546646 - /incubator/xap/trunk/codebase/src/xap/bridges/basic/DefsBridge.js

Author: jmargaris
Date: Tue Jun 12 15:04:29 2007
New Revision: 546646

URL: http://svn.apache.org/viewvc?view=rev&rev=546646
Log:
https://issues.apache.org/jira/browse/XAP-476

Having a getRootDomNode that returned undefined caused problems
because the code checks for the existence of the function, not the return value

Modified:
    incubator/xap/trunk/codebase/src/xap/bridges/basic/DefsBridge.js

Modified: incubator/xap/trunk/codebase/src/xap/bridges/basic/DefsBridge.js
URL: http://svn.apache.org/viewvc/incubator/xap/trunk/codebase/src/xap/bridges/basic/DefsBridge.js?view=diff&rev=546646&r1=546645&r2=546646
==============================================================================
--- incubator/xap/trunk/codebase/src/xap/bridges/basic/DefsBridge.js (original)
+++ incubator/xap/trunk/codebase/src/xap/bridges/basic/DefsBridge.js Tue Jun 12 15:04:29 2007
@@ -52,14 +52,5 @@
 	xap.taghandling.AbstractTagImpl.prototype.init.call( this );
 }
 
-/**
- * We need this because right now &lt;defs&gt; is added to dom root
- * which expects components, we either need to check there for
- * getRootDomNode function or have something like &lt;rootPane&gt;
- * that UI components go into instead of directly under root.
- * This doesn't return anything, it just defines the function
- */
-xap.bridges.basic.DefsBridge.prototype.getRootDomNode = function() {}
-