Some testing-related files using eval()-like functions are hard to be replaced/amended. They are probably going to stay whitelisted from the eval()-assertion. This solution is preferred over manually disabling the assertion in many tests and possibly shadowing the use of eval() in places other than these few, known files. A minimal whitelist of files identified by their full path is going to be hardcoded into the assertion to replace the current pref-based whitelist.
Bug 1560915 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.
Some testing-related files using eval()-like functions are hard to be replaced/amended. They are probably going to stay whitelisted from the eval()-assertion. This solution is preferred over manually disabling the assertion in many tests and possibly shadowing the use of eval() in places other than these few, known files. A minimal whitelist of files identified by their full path is going to be hardcoded into the assertion to replace the current pref-based whitelist. Additionally, it should be ensured that even the whitelisted files are only allowed when running in automation.