Recent Activity

• 

  W3Counter With XHTML

  Ah, no matter, I found my answer here [1]:

  "In HTML, if scripting is enabled, the noscript element is parsed as an CDATA element. If scripting is disabled, it's parsed as a normal element. In XHTML, the element is always parsed as a normal element, and can't really be used to stop content from being present when script is disabled."

  It seems that the tracker image from the <noscript> tag gets fetched regardless with XHTML, hence the duplicates, one with the proper page title and one without. The difference between the duplicates that got displayed under the same visit heading and those which created two separate ones I think was in the case of a referrer being present in the javascript data, which would not be present in the data submitted via the <noscript> image, causing the two hits to be grouped separately (I think).

  Anyway, perhaps there is still some use to noting the issue here, because I can't immediately think of an alternative to provide the same limited tracking when scripting is disabled, unless W3Counter implements some better mechanism to avoid recording such duplication.

  I was very impressed with W3Counter initially, but I have to say that I would hesitate to recommend or buy a subscription to the service without stronger support for progressive industry standards.

  [1] http://wiki.whatwg.org/wiki/HTML_vs._XHTML

  Posted 23 Sep 09 in W3Counter