W3C home > Mailing lists > Public > public-html-comments@w3.org > April 2011

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

From: <benjamin.poulain@nokia.com>
Date: Tue, 26 Apr 2011 15:12:06 +0000
To: <simonp@opera.com>, <public-html-comments@w3.org>
Message-ID: <3309CDAC1BF4B34AB37AC4665E5C343C0493A3@008-AM1MPN1-036.mgdnok.nokia.com>
> > 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.

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

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:26:27 UTC