[Webkit-unassigned] [Bug 14835] createElement(x) v. createElementNS(null, x) v. createElementNS(undefined, x)

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Jul 31 14:50:39 PDT 2007


------- Comment #2 from jcostell at tibco.com  2007-07-31 14:50 PDT -------
Ok, then I guess this bug just comes down to my #1. 

On #2, I hadn't noticed that Firefox's behavior matches Safari's because in
Firefox we just use createElement instead of createElementNS. I happened to
notice the odd difference in behavior between null and undefined only because
of the particulars of our code that wraps the native XML classes. Since on #2
Safari's behavior matches Firefox, I have no complaints other than #1.

Configure bugmail: http://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