Another bug

This is in one of the Atlas JS files:

    this._updatePanel = function(updatePanelElement, rendering, markupContext)
{
        destroyTree(updatePanelElement, markupContext);

                updatePanelElement.innerHTML = rendering;
    }

"innerHTML" is invalid in XHTML Strict / 1.1 I believe. I'm confident
you have to use the DOM.

And you aren't. So it dies a horrid death.

You bad people.

Hi, 

you're right, it's not standard (I think it's a proposed standard though). But
on some browsers it's orders of magnitude faster than the direct DOM tree
manipulation.

IMHO It's a trade-off... in this case should we be standard-compliant or
performant?

Standards-compliant, because it doesn't work otherwise.

It just dies with a Javascript error.

XHTML standard has been out for 5 years now, it shouldn't be this hard to get
anywhere. It's like swimming in treacle.

Hi,

I understand your point. However, it doesn't work in Strict mode, but works in
the other cases (for example, it works in Transitional mode, that I think it's
the officially supported doctype)... it's just another trade-off :)

Do you know if Atlas will support Strict mode in 1.0 release?

If not, I really need to know now so I can tear all the Atlas out of our web
project before it goes live.

XHTML1.1 (which we use) doesn't have a Transitional mode, so that's not an
option for us.

I wish Microsoft had stated somewhere that Atlas was incompatible with Strict
mode before I started using it.