[Webkit-unassigned] [Bug 16401] [GTK] GObject/C DOM binding
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Jan 1 07:19:57 PST 2009
https://bugs.webkit.org/show_bug.cgi?id=16401
------- Comment #124 from lkcl at lkcl.net 2009-01-01 07:19 PDT -------
from the quoted references to "toString" which can clearly be shown
to exist in all the major browser engines - not specifically limited
to "javascript" but to all the major browser engines' generic language
bindings - it can be concluded that leaving out "toString" because it
"isn't in the W3C specification" would be a serious mistake.
that, given the prevalent support for "toString" in all other
competitor products to webkit, users of webkit DOM bindings
_would_ find it irritatingly odd that "toString" is missing.
i have to be honest with you, i was a bit surprised to find that
IE's MSHTML.idl definition file supports it! :)
wine's reverse-engineered version of mshtml.idl is here:
http://source.winehq.org/source/include/mshtml.idl
this illustrates why i have been advocating that javascript's
bindings should be the guiding light.
i trust that i no longer have to go through such extreme lengths
to demonstrate the case for javascript's de-facto standard being
authoritative over the W3C "non-real-world" standard. there are
over 300 objects, 1500 functions and tens of thousands of
properties, and that's _without_ the SVG canvas bindings and
without having enabled HTML5 video support (which i haven't
tried yet).
to have to go through "justifying" every single difference would
be tedious in the extreme.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the webkit-unassigned
mailing list