Difference between revisions of "ATC/Current/SDK/dom - ready"
From Genesys Documentation
m (Text replacement - "\|Platforms?=([^\|]*)PureCloud([\|]*)" to "|Platform=$1GenesysCloud$2") |
m (Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2") |
||
| Line 6: | Line 6: | ||
|Dimension=UtilityMethods | |Dimension=UtilityMethods | ||
|ComingSoon=No | |ComingSoon=No | ||
| − | |Platform=GenesysEngage- | + | |Platform=GenesysEngage-cloud, PureConnect, GenesysCloud |
|Prereq= | |Prereq= | ||
|Section={{Section | |Section={{Section | ||
Revision as of 02:29, July 25, 2020
This topic is part of the manual Journey JavaScript SDK for version Current of Genesys Predictive Engagement.
Contents
Learn how to make a function handler to run when the DOM has fully loaded.
dom - ready
The ready method of the dom module allows you to specify a function handler to run when the DOM has fully loaded. A webpage cannot be altered safely until the document is ready, Journey SDK starts executing regardless of the DOM readiness, and may even fire events before that. Any code reacting to these events that need to modify the DOM should be placed inside the ready handler.
ac('dom', 'ready', function () {
// safely modify the DOM here
});Comments or questions about this documentation? Contact us for support!