On 9/22/17 2:41 AM, Nicholas Nethercote wrote:
This probably won't affect most people, because void strings are a niche feature.
Not in the DOM. They're used anytime you see "DOMString?" in webidl. http://searchfox.org/mozilla-central/search?q=DOMString%3F&path=webidl shows several hundred hits.
Looking at the diff from bug 1401813, it looks like some of the uses are in fact using the XPCOM "void string" feature per se, while some are conceptually trying to represent "JS null" (e.g. in nullable string types about to be passed to JS) and for those having a concept of null string, in the sense defined by dom/base/nsDOMString.h, makes sense.
Put another way, in the new setup the element lifecycle callbacks code in Element::SetAttrAndNotify/UnsetAttr is much more confusing than it used to be...
-Boris _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
