On Fri, Feb 2, 2018 at 10:32 AM, Justin Dolske <[email protected]> wrote:
> > Can I presume that things which now trigger parsing issues are escaped or > errored by the relevant prefs APIs? e.g. if a caller tries to set a pref > name or value with an embedded NULL? > Only the parser has changed. The other APIs are the same. If you try to use an embedded NUL via a C++ API function, it'll just be treated like the string ends at that NUL. I'm not sure what will happen if you use an embedded NUL via a JS API function, though it should be the same behaviour as before. NIck _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
