On the current master/beta (d25c9a0), when visiting Special:EditWatchlist the following error is generated in the js console:
Uncaught TypeError: Cannot read properties of null (reading 'toString')
at HTMLSelectElement.eval (limitSelectors.js:28:69)
at jQuery.each (jquery.js:383:19)
at jQuery.fn.init.each (jquery.js:205:17)
at module.exports (limitSelectors.js:27:18)
at HTMLDocument.eval (init.js:8:3)
at mightThrow (jquery.js:3489:29)
at process (jquery.js:3557:12)Doesn't appear to be causing any noticeable faults, but FYI
Derived Requirement
Visiting *Special:EditWatchlist* must not trigger JavaScript runtime errors.
All JavaScript executed on page load, including logic in limitSelectors.js, must safely handle null or missing values and must not throw uncaught exceptions.
The page must load cleanly with no console errors, regardless of user state or watchlist configuration.
Test Steps
Test Case 1: Verify no JavaScript errors occur when loading Special:EditWatchlist
- Log in to the wiki.
- Open browser developer tools and switch to the Console tab.
- Navigate to *Special:EditWatchlist*.
- Observe the console output during and after page load.
- ✅❓❌⬜ AC1: Confirm no uncaught JavaScript errors are logged, including errors related to calling toString() on null.
Test Case 2: Verify page loads correctly with modified watchlist settings
- Modify watchlist settings (e.g., change limits, filters, or preferences if available).
- Navigate again to *Special:EditWatchlist*.
- Observe the console output.
- ✅❓❌⬜ AC2: Confirm JavaScript executes safely with non-default values and no uncaught errors occur.
Test Case 3: Verify error does not reappear after page refresh
- While on *Special:EditWatchlist*, refresh the page.
- Monitor the JavaScript console.
- ✅❓❌⬜ AC3: Confirm the Cannot read properties of null (reading 'toString') error does not appear after refresh.
QA Results -Beta
| AC | Status | Details |
|---|---|---|
| 1 | ✅ | T412812#11466858 |
| 2 | ✅ | T412812#11466858 |
| 3 | ✅ | T412812#11466858 |
