Opened 13 years ago

Closed 13 years ago

#5574 closed enhancement (fixed)

Dojo should use DOMContentLoaded with WebKit >= 525

Reported by: guest Owned by: James Burke
Priority: low Milestone: 1.3
Component: General Version: 1.0
Keywords: Cc:
Blocked By: Blocking:

Description

Nightly builds of WebKit support the DOMContentLoaded event in a similar manner to Gecko. Dojo should make use of this for WebKit versions >= 525 to avoid the nasty timer-based hack being used in future versions of WebKit-based browsers.

Change History (4)

comment:1 Changed 13 years ago by alex

Milestone: → 1.1
Owner: changed from anonymous to alex
Status: new → assigned

comment:2 Changed 13 years ago by dylan

Milestone: 1.1 → 1.2

comment:3 Changed 13 years ago by bill

Milestone: 1.2 → 1.3
Owner: changed from alex to James Burke
Status: assigned → new

comment:4 Changed 13 years ago by James Burke

Resolution: → fixed
Status: new → closed

(In [15430]) Fixes #5574 and Fixes #7696. dojo.isChrome and dojo.isWebKit available. dojo.isWebKit now gives version numbers like 525.3. KHTML detection changed to just support being defined for KHTML browsers only, since other KHTML-related browsers are likely more sensitive to dojo.isWebKit versions. Changed dojo.isSafari check so that now Safari 3.1.2 now correctly reports as dojo.isSafari 3.1. But with that change, Chrome browser does not have dojo.isSafari defined, which should be good, since we now have dojo.isWebKit and then dojo.isChrome for chrome-specific (non-webkit) issues. Now that there are webkit numbers, switched to DOMContentLoaded for webkit versions that support it. \!strict

Note: See TracTickets for help on using tickets.