Bug #20637
closed
Remove ancient blurLink code
Added by Michiel Roos over 15 years ago.
Updated over 11 years ago.
Description
I know I can use config.removeDefaultJS, but that will also kill my spam protection rules.
The only way I can get around this is by making my own JS file for the email spam protection JS and then setting config.removeDefaultJS to 1
I think the time has come to give the blurLink code and other default JS code an overhaul.
At least make the blurLink code more configurable. Like not including it when config.noBlur = 1
The best would be to get rid of it completely and only putting it back when config.iCanHazBlurCode = 1
??
(issue imported from #M11367)
Files
attached patch allows
config.noBlur = 1
to get rid of the
// Blurring links:
function blurLink(theObject) { //
if (msie4) {theObject.blur();}
}
Good idea!
What about the second part of the patch? I don't see a reason for a closing bracket. Bug?
- ' . $JSef0;
+ ') . $JSef0;
no, that's part of the condition :)
But that's not enough. Also the link generation should be aware of this config, which makes it more complex. I will look at this now.
Any news here?
This blurLink stuff sucks... still in version TYPO3 4.4
Yeah, I think that function is not needed anymore. Far away from beeing state of the art.
Attached is a patch that removes the whole functionality, because this should not be done at all with inline JS.
- Category deleted (
Communication)
- Assignee deleted (
Steffen Kamper)
- Target version deleted (
0)
Not sure if it's our configuration - but I guess this one is resolved since 4.7.x where a lot of stuff has been improved regarding the whole frontend output generation. At least I cannot see anything regarding blur in our whole FE output.
Can someone confirm my guess and close this issue if I'm right?
- Status changed from Accepted to Closed
Also available in: Atom
PDF