We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In javascript we could add:
requestAnimationFrame(function() { Array.prototype.forEach.call( document.querySelectorAll('a[href^="javascript:linkTo_UnCryptMailto"]'), function(link) { link.innerHTML = link.innerHTML.replace(' (at) ', '@')} ); });
The text was updated successfully, but these errors were encountered:
Good idea! Is there a reason why requestAnimationFrame should be used? I guess a dom ready event would be sufficient here.
requestAnimationFrame
We should put that behind an option though, I think there might be a number of crawlers with headless JS where that might disable the "protection"
Sorry, something went wrong.
I added requestAnimationFrame only to improve the speed, the transformation can happen after an initial paint to not slow things down.
I have no ideas about modern crawlers, for headless js probably " (at) " is also very obvious. But we could add a 3sec delay.
No branches or pull requests
In javascript we could add:
The text was updated successfully, but these errors were encountered: