Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Is `dom.disable_beforeunload` still necessary?
See original GitHub issueI got bit by this on a form I was building and testing on several browser for the typical user warning like “Hey the form is not complete yet do you want to close the page?”.
On a profile with arkenfox the warning is not triggered and the page is closed with form data lost.
I think the abuse of warning spam is something that got fixed (I believe?) by browsers some time ago by hardening the requirements to enable the beforeunload event.
AFAICS last time this was touched was 5 years ago, is this still a concern?
Should there be a warning in the user.js comments informing of potential sideffects of the switch?
https://github.com/arkenfox/user.js/blob/f4187632faef76df4de0cbb0cdc7199f22fadd76/user.js#L611-L614
Thank you!
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
If sites abuse it, you can disable it on a per site basis using uB’s
+js.One override less. Thanks.
DONE - https://github.com/arkenfox/user.js/pull/1558/commits/070b08aea0c8eb37823381be546672792f831ac8