Remove beforescriptexecute/afterscriptexecute#1103
Merged
Conversation
These have failed to garner implementer interest beyond one engine. Fixes #943.
Merged
|
This was a bad move. There is no alternative way of controlling script execution, it may be a niche feature, but has its purpose for user scripts, web extensions and other client-side blocking software. |
Member
|
Browsers can expose any events to user scripts and extensions. |
|
In a totally unstandardized way. This is about interoperability after all. |
|
In case this is revisited in the next update to the standards, one very compelling use case for the existence of this event is to enable a new class of very effective XSS mitigation techniques: https://www.researchgate.net/publication/320748079_WebMTD_Defeating_Web_Code_Injection_Attacks_using_Web_Element_Attribute_Mutation |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
These have failed to garner implementer interest beyond one engine.
Fixes #943.
I think we've given these enough of a shot. Similar to other single-vendor features (including both unloved ones, like showModalDialog, and loved ones, like MediaController) we should be removing them.
Related: #1100.