Boris Zbarsky bzbar...@mit.edu wrote:
On 3/3/10 12:11 PM, Stewart Brodie wrote:
As far as I can tell, this affects: HTMLSelectElement.add(),
HTMLOptionsCollection.add(), Node.appendChild(), Node.replaceChild(),
Node.insertBefore().
Is it option-specific, though? Last I checked, various
On Mar 4, 2010, at 2:27 AM, Stewart Brodie wrote:
Boris Zbarsky bzbar...@mit.edu wrote:
On 3/3/10 12:11 PM, Stewart Brodie wrote:
As far as I can tell, this affects: HTMLSelectElement.add(),
HTMLOptionsCollection.add(), Node.appendChild(), Node.replaceChild
(),
Node.insertBefore().
Is
On Thu, 04 Mar 2010 11:27:23 +0100, Stewart Brodie
stewart.bro...@antplc.com wrote:
Boris Zbarsky bzbar...@mit.edu wrote:
On 3/3/10 12:11 PM, Stewart Brodie wrote:
As far as I can tell, this affects: HTMLSelectElement.add(),
HTMLOptionsCollection.add(), Node.appendChild(),
Anne van Kesteren ann...@opera.com wrote:
On Thu, 04 Mar 2010 11:27:23 +0100, Stewart Brodie
stewart.bro...@antplc.com wrote:
Boris Zbarsky bzbar...@mit.edu wrote:
On 3/3/10 12:11 PM, Stewart Brodie wrote:
As far as I can tell, this affects: HTMLSelectElement.add(),
On Thu, 04 Mar 2010 13:05:13 +0100, Stewart Brodie
stewart.bro...@antplc.com wrote:
Is this documented anywhere?
On some W3C mailing list archive I think.
By compatibility problems, presumably you
mean bugs in Firefox that were then exploited by content authors who
didn't know better?
Apart from compatibility issues, there's also the fact that requiring
explicit adopt/import is a pointless burden on authors.
Rob
--
He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We
The algorithm in the HTML5 specification for attaching an option element to
a select element is incomplete, because it doesn't describe how to handle
the case where the option element does not belong to the same document as
the select element.
It seems that HTMLOptionElement objects are immune
Was your testing done with option elements created with
document.createElement(option) or new Option? I ask because I seem to recall
the behavior being different for at least some types of elements.
-- Darin
Darin Adler da...@apple.com wrote:
Was your testing done with option elements created with
document.createElement(option) or new Option? I ask because I seem to
recall the behavior being different for at least some types of elements.
That's a good idea - I forgot to test that. I've updated
On 3/3/10 12:11 PM, Stewart Brodie wrote:
As far as I can tell, this affects: HTMLSelectElement.add(),
HTMLOptionsCollection.add(), Node.appendChild(), Node.replaceChild(),
Node.insertBefore().
Is it option-specific, though? Last I checked, various browsers
implicitly adopted on
10 matches
Mail list logo
