RE: What are we trying to solve with document.designMode?

> > With my current understanding of the problem, I think this should be
> > removed from the specification or explicitly deprecated. The differences
> > between released browser make the attribute unreliable for web authors.
> > I could not find in the archives why designMode was added to the spec, I
> > would be interested to the rationale behind this feature.
> 
> designMode is needed for Web compat. If the spec doesn't match browsers,
> please file spec bugs.

In the same manner, window.find() is largely deployed but did not make it to the spec. It seems a bit arbitrary to have designMode.

cheers,
Benjamin

Received on Tuesday, 26 April 2011 15:13:39 UTC