There is also example 13 NiftyLoad that addresses this issue by preserving the previous onLoad.  However, this wouldn't help if something steps on Nifty's onLoad.

 My preference is to use Dojo's event framework and simply "connect" to the onload event.