undef causes a JS error, undefined seems to be the correct term to use
Created attachment 76882 [details] [review] Bug 21064: Use undefined instead of undef To test: 1 - Load the advanced cataloging editor 2 - Refresh the page several times 3 - Check the JS console, you shoudl see an error: 'undef is not defined' 4 - Apply patch 5 - Try again, should be no error
Created attachment 76963 [details] [review] Bug 21064: Use undefined instead of undef To test: 1 - Load the advanced cataloging editor 2 - Refresh the page several times 3 - Check the JS console, you shoudl see an error: 'undef is not defined' 4 - Apply patch 5 - Try again, should be no error Signed-off-by: Pierre-Luc Lapointe <pierreluc.lapointe@inLibro.com>
Created attachment 77065 [details] [review] Bug 21064: Use undefined instead of undef To test: 1 - Load the advanced cataloging editor 2 - Refresh the page several times 3 - Check the JS console, you shoudl see an error: 'undef is not defined' 4 - Apply patch 5 - Try again, should be no error Signed-off-by: Pierre-Luc Lapointe <pierreluc.lapointe@inLibro.com> Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de>
Awesome work all! Pushed to master for 18.11
Pushed to 18.05.x for 18.05.03
Pushed to 17.11.x for 17.11.10