[Webkit-unassigned] [Bug 27432] add read-write access to HTMLOptionElement text under GObject bindings

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jul 24 01:09:17 PDT 2009


https://bugs.webkit.org/show_bug.cgi?id=27432


Maciej Stachowiak <mjs at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mjs at apple.com




--- Comment #13 from Maciej Stachowiak <mjs at apple.com>  2009-07-24 01:09:17 PDT ---
Since HTML5 says the property should be read-only, we should do one of the
following:

1) If other browsers make it read-write to JavaScript, we should propose a
change to the HTML5 spec, and eventually make the property read-write for all
language bindings.

2) If other browsers have it read-only, then we should eventually fix our
JavaScript binding for this property to be read-only as well, and in the
meantime not propagate the mistake to other bindings.

In any case, it seems like leaving the property read-only for other bindings is
safer in the short term, since it would be an API break to remove the setter
but not an API break to add it. In addition, the right outcome here is clearly
less ifdefs not more - so adding an extra conditional doesn't move the code in
the right direction.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list