Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#17074 closed defect (fixed)

auto-require issues in Chrome

Reported by: haysmark Owned by: bill
Priority: undecided Milestone: 1.9
Component: Parser Version: 1.9.0b2
Keywords: Cc:
Blocked By: Blocking:

Description

See:

http://archive.dojotoolkit.org/nightly/checkout/dijit/tests/layout/robot/GUI.html http://archive.dojotoolkit.org/nightly/checkout/dijit/tests/tree/robot/Tree_a11y.html

In the latest Chrome 26, the test page will load as normal, but the actual test script will not execute. The robotx created iframe containing the test never receives the load event from the underlying non-robot page; is the parser eating the load event for some reason?

The page shows a warning about several auto requires. If you manually add everything it complains about to the underlying non-robot test (bewaring of caching issues of course), the load event will fire.

Change History (4)

comment:1 Changed 7 years ago by bill

Milestone: tbd1.9
Status: newassigned

Thanks, I'll add the requires. Not sure what's going on, but this wil all change for 2.0 anyway, since dojo.ready() is being EOL'd and the test runner needs a different way to tell when the page has finished initializing. I think this is more of a DOH issue than a Parser issue.

comment:2 Changed 7 years ago by bill

Resolution: fixed
Status: assignedclosed

In [31367]:

stop using auto-require in some dijit tests, fixes #17074

comment:3 Changed 7 years ago by bill

In [31371]:

Fix more dijit tests to stop using auto-require, and fix race condition in ContentPaneLayout.html causing spurious failures. Refs #17074.

comment:4 Changed 7 years ago by bill

In [31419]:

Fix another test to stop using auto-require, refs #17074.

Note: See TracTickets for help on using tickets.