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

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

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 19 Jul 2011 19:44:04 +0000 (UTC)
To: benjamin.poulain@nokia.com
cc: simonp@opera.com, public-html-comments@w3.org, "ext Jukka K. Korpela" <jukka.k.korpela@kolumbus.fi>
Message-ID: <Pine.LNX.4.64.1107191942560.2079@ps20323.dreamhostps.com>
On Tue, 26 Apr 2011, benjamin.poulain@nokia.com wrote:
> > > 
> > > 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.

They are being handled in the same way, as far as I can tell. 
window.find() is still an open issue.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 19 July 2011 19:44:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 19:44:39 GMT