[embjopr-issues] [JBoss JIRA] Closed: (EMBJOPR-101) Nav tree JS object (Tree.Item) is not ready after page refresh, causing ScriptException: TypeError: Cannot call method "fireExpansionEvent"

Ondrej Zizka (JIRA) jira-events at lists.jboss.org
Tue Jul 19 12:06:24 EDT 2011


     [ https://issues.jboss.org/browse/EMBJOPR-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ondrej Zizka closed EMBJOPR-101.
--------------------------------

    Resolution: Out of Date


We will probably switch to Selenium because HTMLUnit is not able to cope with latest javascript tricks in jQuery et al.

> Nav tree JS object (Tree.Item) is not ready after page refresh, causing ScriptException: TypeError: Cannot call method "fireExpansionEvent"
> -------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: EMBJOPR-101
>                 URL: https://issues.jboss.org/browse/EMBJOPR-101
>             Project: Embedded Jopr
>          Issue Type: Task
>            Reporter: Ondrej Zizka
>            Assignee: Stan Silvert
>              Labels: ScriptException, TreeItem, TypeError, ajax, javascript, navtree
>
> Right after page is loaded and test thread is running, JavaScript function object `Tree.Item` is not initialized yet.
> This function is created in an externally loaded file, admin-console/a4j/g/3_3_0.GAorg/richfaces/renderkit/html/scripts/tree-item.js  .
> This problem appears when we click() in tests on some tree node after page load.
> It is unlikely that user will be clicking fast enough to trigger this error, moreover IMHO Firefox blocks JS execution until external JS files are all loaded (but not sure), so this is only problem for QA.
> Currently we solve this by calling NavTree#waitUntilReady( int intervalMs, int retries )  - e.g. in getNavTreeArrow():
>   ejtt.navTree.waitUntilReady(100, 15);
> HTMLUnit's JavaScriptEngine#isScriptRunning() doesn't solve this, because AJAX's async calls' TimeOuts are not considered as running javascript (only when the timer's handler is called).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the embjopr-issues mailing list