The widget template
Check a widget's root identifier and startup callback before studying its guest code.
This original, minimal illustration retains the historic /template/ route. It is documentation rather than a running legacy widget.
<div id="DEMO_">
<p id="DEMO_MESSAGE">Ready.</p>
<script>
ADSAFE.go("DEMO_", function (dom) {
"use strict";
dom.q("#DEMO_MESSAGE").value("Started.");
});
</script>
</div>What to check
The containing identifier and the string supplied to ADSAFE.go agree. The child identifier uses the root's prefix. The callback operates through dom. Historical validation rules and a matching runtime are still required; a template alone does not establish isolation.
Read Widget Structure for the full explanation. The upstream widget template is the historical primary source.