New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove installable 'natives' feature that modifies String and RegExp prototypes #89
Comments
Hm, interesting. There's very little benefit to adding this option, since it would save almost no code, the "natives" option is already self-contained and not relied on by the rest of the code, and native overrides are already off by default. You'd essentially just need to comment out xregexp.js#L376-L380 or kill the |
Fair enough. I'm not saying the addons validator is sane, but as it's going
to be enforced on all Firefox extensions, I have to dance to its tune.
|
Would be happy to see a pull request that showed how a custom build that worked around this problem would work and be set up. I'm also considering removing support for |
That's in essence what my pull request would do. |
Before reading the above I was going to suggest something similar. Move |
|
Super. Any timeline on a release which would contain this change? |
This will be included in v4.0.0. Sorry, no timeline at the moment. There's no required delay before releasing v4.0.0, but I would like to bundle the drop of support for |
After making this change, will also want to update |
@retorquere this is finally completed and included in v4.0.0, thanks to @josephfrazier. |
I'm including xregexp in a firefox extension, and the changes to RegExp.prototype and String.prototype don't pass the impending extension signature validation. Is it possible to get an xregexp build that doesn't make these modifications to these prototypes?
The text was updated successfully, but these errors were encountered: