Posted on: 12/01/04 04:28pm
By: ronack
I had a link like this
<a href="void(window.open('http://domain/page.php', '', 'width=720,height=500, location=no, menubar=no, status=yes, toolbar=no, scrollbars=yes, resizable=yes'))">Click here </a>
It doesn't work now. What's different?
Broken JS link after upgrade to 1.3.10
Posted on: 12/01/04 04:35pm
By: Turias
Try replacing void with javascript:void
I can't get the link you posted to work without doing that.
Broken JS link after upgrade to 1.3.10
Posted on: 12/01/04 04:40pm
By: ronack
[QUOTE BY= Turias] Try replacing void with javascript:void
I can't get the link you posted to work without doing that.[/QUOTE]It just strips out the javascript:
Do I need to wrap it with the code: tag?
Broken JS link after upgrade to 1.3.10
Posted on: 12/01/04 04:43pm
By: ronack
No that didn't work.
Broken JS link after upgrade to 1.3.10
Posted on: 12/01/04 04:53pm
By: Dirk
javascript: is not in the list of allowed protocols and is therefore removed.
// list of protocols that are allowed in links
$_CONF['allowed_protocols'] = array ('http:', 'https:', 'ftp:');
Although I don't think it would be a good idea to add it there ...
bye, Dirk
Broken JS link after upgrade to 1.3.10
Posted on: 12/01/04 04:59pm
By: ronack
Yeah I would need it for admin only, but I do use it a lot and it is a show stopper for me.
Broken JS link after upgrade to 1.3.10
Posted on: 12/01/04 05:01pm
By: ronack
Are stories the only place JS is not allowed?
Broken JS link after upgrade to 1.3.10
Posted on: 12/01/04 05:10pm
By: Dirk
The protocol check is part of the kses filter, so it would apply to all places where that filter is used. I.e. articles, comments, static pages (if you enable HTML filtering for static pages), the forum (if configured to use Geeklog's HTML filter instead of its own), etc.
bye, Dirk
Broken JS link after upgrade to 1.3.10
Posted on: 12/01/04 05:33pm
By: ronack
Looks I am going to have to enable it in the allowed protocals for now. I'm just using it in too many places.