Amadesa Tags Insight

.highlightedText {BACKGROUND-COLOR: #ffff00;} Frequently, I am getting questions about the Amadesa tags. What is amPid and amPPid?, how to use amParams?, but the question that I get the most is “why there is a closing tag without an opening one?” and “I have an XHTML compliant web site. I cannot have a closing tag without an opening one. How can I make the tags XHTML compliant?” In this article I will answer both questions, but first we need to understand what is a tag is needed by Amadesa in the 1st place. What is a

html tag is intended to signal to the browser to render the HTML within the opening and closing <noscript> tag only if the browser does not support JavaScript (for more information click here). In other words, the browser totally ignores the content within this tag, if the browser does support JavaScript. If there is an image tag within it, it will not be visible to the user and moreover, the image will not be downloaded to the browser. Why is a

tag needed by the Amadesa Element Tag? Amadesa is using the

liveExperience('element1');

Untested area. This text should is not tested. The liveExperience() function call is part of the Amadesa tag and it’s responsibility it to download the alternate image to be tested for “element1”. If an alternate content is not found (not test defined/deployed live) or the “Control” version was chosen, nothing happens on the page and both the image and the text will appear. However, when a tested version is defined, the liveExperience() call downloads the alternate HTML and writes it to the page via document.write. Immediately after that it writes an opening lt;noscriptgt; to the page (using document.write() as well). Let’s take a look at the generated HTML after the call to liveExperience(). I am using FireFox and FireBug to illustrate the generated HTML: You can see that the alternate HTML (in our case the image to be tested) exist on the page and the original content (i.e the Control version) is wrapped within a tag is needed because the liveExperience() call is injecting the opening tag? If you remove the closing tag, the browser will not find the closing for the opening one and will generate one automatically at the end of the without an opening one. This can be undesirable by some organizations because they are are required to be XHTML compliant. The Amadesa tag can be changed to be an XHTML compliant tag with few minor tweaks. To illustration that, I changed the above tag to be XHTML compliant and highlighted the changed areas:

Untested area. This text should is not tested. Notice that I added an opening

. This solution ensures that the tag is XHTML compliant but most importantly also ensures that only the wanted content (in our case an image) is hidden and untested areas are not touched. The above solution works and tested on the IE 6 and up, FF 2 and up, Chrome, Safari, and Opera.

← Back to Blogs

Subsribe to RSS Follow Us on Twitter Become a Fan LinkedIn