Hi! I'm building a CMS with lots of forms in dialogs. Its working great, but I'm a bit concerned abaout the flickering going on when a dialog is rendered. First it opens with a loading message, then when the content is loaded the dialog is being centered and correctly aligned. Then the parsing takes place and one can see the form objects being rendered leading to more flickering.
onLoad
Add onLoad with *method* to djConfig
Submitted by afisk on Wed, 08/13/2008 - 20:10.
I'd love to see a new onLoadFunc property, or some similar name, in djConfig. This would allow a script to programmatically grab an xdomain version of dojo that automatically calls the specified function when it's loaded, getting around asynchronous loading issues.
For example, I have a bit of javascript I'd like to be loaded in a single call from third-party pages, and my script uses Dojo. To get around those sites having to include the Dojo script as well as mine in their HTML, I'd like to programmatically load it as in:
function onDojoLoad()
{
Firefox 3 fires the DomContentLoaded event prematurely
Submitted by jmr76 on Mon, 07/14/2008 - 21:01.
I've run into an issue with Firefox 3 firing its DomContentLoaded event before all of the inline javascript and required dojo libraries have been pulled into the context. Has anyone else here noticed a similar issue with the latest relase of Firefox 3? I can readily reproduce the problem using FF3 on WinXP (the mozilla folks have also been able to reproduce it with FF3 on Vista).
We've reported a bug to Mozilla here: https://bugzilla.mozilla.org/show_bug.cgi?id=444322
ContentPane onLoad again
Submitted by stefan0101 on Thu, 07/10/2008 - 11:09.
Hi,
I'm rather new to dojo so hello everybody.
I am currently stuck in a topic which already came up several times, but I couldn't find a satisfying answer.
I'm trying to populate a contentPane using a external file. Something like
<div dojoType="dijit.layout.ContentPane" href="content.htm"></div>
In content.htm I'd like to do some js setup after beeing loaded. In the dojo documentation it is stated that dojo/method script tags are evaluated in the loaded content. Therefore my content.htm looks like
Error: dojo.body() is null or not an object !!
Submitted by gmilega on Thu, 05/01/2008 - 15:23.
I have web application built on JSP, with dojo included on each page it is used (almost every page).
If during browsing i am not waiting for pages to fully load and navigate to another one,
dojo throws a java script exception
"Error: dojo.body() is null or not an object"
As far as i understand dojo thinks it is loaded but navigating to another page spoils it's plannes.
this function throws this
onload: function(){
// summary:
// Function that detects if we are in high-contrast mode or not,
onload race condition in IE
Submitted by nkolba on Mon, 01/14/2008 - 15:04.
I am seeing what looks like a race condition occurring in Internet Explorer, where it seems that the onload event for dojo is firing before the DOM is fully loaded. This is on a very large page with many inline javascript blocks. The behavior that I am seeing is as follows:
1. A flag indicating the body is loaded is set in a function attached using dojo.addOnLoad.
2. Some code in an inline script checks this flag, and finds that the body is loaded, however, the DOM is not fully loaded.
Onload event is never called
Submitted by rraaff on Thu, 11/29/2007 - 16:02.
I have page which use the onload event, but when I include the dojo library that event is enver called.
The page is as simple as follow:
<head>
<title>Transiciones</title>
<script src="js/dojo/dojo.js"></script>
</head>
<body onload="alert(1)">
</body>
<title>Transiciones</title>
<script src="js/dojo/dojo.js"></script>
</head>
<body onload="alert(1)">
</body>
The problem appears only in IE and the dojo version I'm using is 0.3.1.
Page Load / Unload
Submitted by MattBowen on Tue, 06/05/2007 - 18:37.
To perform any DOM scripting, one needs a DOM to work with. Otherwise, you don't have nodes to attach your events to or manipulate, and the results of your program can be undesirable (e.g., no output for no obvious reason, or events attached to the document root).
