Greetings, I just landed the patches for bug 1489047, which remove the DOMString type from XPIDL.
Why? Here are details about how string types in XPIDL and WebIDL are converted from JS to C++: - XPIDL AString: `undefined` becomes Void, `null` becomes Void. - XPIDL DOMString: `undefined` becomes "undefined", `null` becomes Void. - WebIDL DOMString: `undefined` becomes "undefined", `null` becomes "null" unless `[TreatNullAs=EmptyString]` is used. Also, `DOMString?` can be used to get the XPCOM AString behavior. In other words, XPIDL DOMString was almost-but-not-quite-identical to both XPIDL AString and WebIDL DOMString. All the actual web-facing DOM stuff is now defined via WebIDL, so there didn't seem much point in keeping XPIDL DOMString. Nick _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
