Currently, if an invalid value is passed to one of the Reader View prefs, it stops `AboutReader.sys.mjs` from executing and makes reader view accessible. We should refactor the code by declaring all pref values using the default values first, then attempt to fetch the pref value in a try catch block, logging a warning if an invalid value is passed.
Bug 1894763 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Currently, if an invalid value is passed to one of the Reader View pref getters, it stops `AboutReader.sys.mjs` from executing and makes reader view accessible. We should refactor the code by declaring all pref values using the default values first, then attempt to fetch the pref value in a try catch block, logging a warning if an invalid value is passed.
Currently, if an invalid value is passed to one of the Reader View pref getters, it stops `AboutReader.sys.mjs` from executing and makes reader view inaccessible. We should refactor the code by declaring all pref values using the default values first, then attempt to fetch the pref value in a try catch block, logging a warning if an invalid value is passed.
blocker level bug for rolling out new theme and layout menus. Currently, if an invalid value is passed to one of the Reader View pref getters, it stops `AboutReader.sys.mjs` from executing and makes reader view inaccessible. We should refactor the code by declaring all pref values using the default values first, then attempt to fetch the pref value in a try catch block, logging a warning if an invalid value is passed.