[TIMOB-6755] MobileWeb: Use DOMReady instead of window.onload
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | High |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2011-12-20T13:45:31.000+0000 |
| Affected Version/s | Release 2.0.0 |
| Fix Version/s | Sprint 2011-51, Release 2.0.0, Release 1.8.1 |
| Components | MobileWeb |
| Labels | merge-1.9.0 |
| Reporter | Chris Barber |
| Assignee | Chris Barber |
| Created | 2011-12-19T10:10:46.000+0000 |
| Updated | 2017-03-03T23:20:10.000+0000 |
Description
Mobile web attaches to window.onload when it should use DOMReady. DOMReady fires before window.onload, thus possibly speeding up the application launch. Lastly, by binding to window.onload, it's possible for mobile web's onload handler to get overwritten by plugins.
Pull request: https://github.com/cb1kenobi/titanium_mobile/pull/13
Merged in to cb1kenobi's repo until 1.8->1.9 transition is stable in appcelerator repo.
Closing ticket as MobileWeb is no longer supported.