Hi Jake,
thanks very much!
Just to wrap up this thread, here just two more links:
(once knowing, this comes from dynamic script insertion - it
becomes a "known issue")
Last question:
Is there a way to suppress the warning, so users of
Ajaxify aren't irritated?
I would love to unroot this issue properly, but also see no way of
doing so, as the injected scripts should be inserted in the head
before the other HTML content...
(e.g. there would be a
way of setting
programmatically before the injection, but that would result in
undesired behaviour)
So, I agree, that there is nothing that can be done, except maybe
suppressing the warning...
Thanks once again!