Boris Zbarsky:
> > If the return value of lookupNamespaceURI is |undefined|, should that
> > stringify to "" or "undefined"? Same question for |null|.
> >
> > Note that I'm not sure there's an obvious way to annotate this in web
> > idl yet.
Cameron McCormack:
> Yeah, there’s no way to specif
Boris Zbarsky wrote:
If the return value of lookupNamespaceURI is |undefined|, should that
stringify to "" or "undefined"? Same question for |null|.
Note that I'm not sure there's an obvious way to annotate this in web
idl yet.
Since NSResolver has now been removed, I'm closing this issue.
Sam Weinig wrote:
I believe undefined and null (as well as the empty string) should turn
into null.
"While resolving either a prefix or the default namespace, if the
lookupNamespaceURI() method returns undefined or an empty string, the
implementation must act as if null had been returned."
I believe undefined and null (as well as the empty string) should turn
into null.
"While resolving either a prefix or the default namespace, if the
lookupNamespaceURI() method returns undefined or an empty string, the
implementation must act as if null had been returned."
On Jul 11, 200
Boris Zbarsky:
> If the return value of lookupNamespaceURI is |undefined|, should that
> stringify to "" or "undefined"? Same question for |null|.
>
> Note that I'm not sure there's an obvious way to annotate this in web
> idl yet.
Yeah, there’s no way to specify this at the moment. We coul
If the return value of lookupNamespaceURI is |undefined|, should that
stringify to "" or "undefined"? Same question for |null|.
Note that I'm not sure there's an obvious way to annotate this in web
idl yet.
-Boris
