Custom Query (18300 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (37 - 39 of 18300)

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
Ticket Resolution Summary Owner Reporter
#13409 fixed xdomain test failures Rawld Gill haysmark
Description

See:

http://archive.dojotoolkit.org/nightly/checkout/dojo/tests/_base/loader/xdomain/xdomain.html

In IE6, I get the following failures:

FAILED test: ../../dojo/tests/_base/loader/xdomain/xdomain.html::xdomain::undefined assertEqual() failed:
      		 expected
      		 		 true
      		 but got
      		 		 false

       with hint: 
      		 		 failed at id=18
       859ms
FAILED test: ../../dojo/tests/_base/loader/xdomain/xdomain.html::xdomain::undefined assertEqual() failed:
      		 expected
      		 		 true
      		 but got
      		 		 false

       with hint: 
      		 		 failed at id=19
       812ms
FAILED test: ../../dojo/tests/_base/loader/xdomain/xdomain.html::xdomain::undefined assertEqual() failed:
      		 expected
      		 		 true
      		 but got
      		 		 false

       with hint: 
      		 		 failed at id=18
       484ms
FAILED test: ../../dojo/tests/_base/loader/xdomain/xdomain.html::xdomain::undefined assertEqual() failed:
      		 expected
      		 		 true
      		 but got
      		 		 false

       with hint: 
      		 		 failed at id=19
       297ms
#13255 fixed xdomain mode and build are not 100% backcompat Rawld Gill Rawld Gill
Description

Consider the following legacy module:

dojo.provide("myApp.myModule");

// Section A

dojo.require("myApp.myOtherModule);

// Section B

As of 1.7b1, this is transformed (both in a build and during on-the-fly xdomain loading) to:

define("myApp/myModule", ["dojo", "dijit", "dojox", "myApp/myOtherModule"], function(dojo, dijit, dojox){

// Section A
// Section B
});

This yields the code path:

  1. myApp/myOtherModule
  2. Section A
  3. Section B

In most cases, this is OK since Section A is empty. However, when Section A is not empty, this is different than version v1.6- which would ensure the code path:

  1. Section A
  2. myApp/myOtherModule
  3. Section B

Both the loader and the builder should be improved to ensure the correct backcompat code path.

Since the alternative (v1.7b1) code path allows for some optimizations (for example, the loader doesn't have to guarantee an entire dependency tree is downloaded before starting to execute modules), it should be retained as an option.

#13194 worksforme xdomain loads never fire domReady Rawld Gill Mark Wubben
Description

We're serving our assets from a different domain than the main pages, even during development. In trunk, domReady never fires:

Test case:

<!doctype html>
<script src="http://assets.eqm/scripts/dojo/dojo.js"></script>
<script>
require(["dojo/domReady!"], function(){
  alert("Ready");
});
</script>

This works fine from assets.eqm, but fails on assets2.eqm (set up as a server alias, so serving the exact same file).

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
Note: See TracQuery for help on using queries.