424cae173b
In particular, 0 is kept as a value, and passing undefined to setField now throws an error. I'm not sure if we actually want to return an empty string in all cases for missing/invalid fields, but that's what we do currently. |
||
---|---|---|
.. | ||
components | ||
content | ||
resource | ||
tests | ||
chrome.manifest | ||
install.rdf | ||
runtests.sh |