> What mattcoz is describing is unfortunately *not* what you (Dieter) are
> experiencing.
> Explanation: In the Firefox nightly builds starting back in September there
> was a bug, that caused the Script panel to always show "No JavaScript on
> this page" (see bug 689101<
https://bugzilla.mozilla.org/show_bug.cgi?id=689101>
> ).
> Though this just affected Firefox Aurora (9.0a2) and Nightly (10.0a1) and is
> unrelated to FF 7.0.1, so your problem is unfortunately not solved by the
> fix of bug 689101.
unfortunately!
> It's quite often used to store templates because the script tag prevents the
> content from being rendered.
>
> Yes, the script tag prevents the code from being displayed, though I still
> wonder, why you put HTML code into a <script> tag. Sorry to say, but it
> looks to me like abusing the script tag, because as its name says, it should
> just contain scripts.
>
> Usually the templates are in one or more external html files and loaded on
> demand using an ajax call.
>
> Ok, but after that AJAX call you have the contents of that file in a
> variable. So why do you need to save it into a <script> tag?
I cannot really "defend" this method and agree that is seems a little
odd but it seems to have been introduced by John Resig himself (http://
ejohn.org/blog/javascript-micro-templating) in his original micro
templating blog entry and is widely used (at least) in the jQuery
universe.
> While I am not convinced of that method your problem could still be a bug in
> Firebug (or Firefox). So you should test your test case from above in a
> fresh Firefox profile and tell us, if the problem is gone. If yes, it might
> be some preference or a conflict with another extension. Please also read
> the steps described at I found a Firebug Bug!<
http://getfirebug.com/wiki/index.php/I_found_a_Firebug_Bug%21>.
> Please tell us then, if your problem persists. If so, we'll need to find a
> test case we can reproduce, too.
1) I have again tried to debug my original application using a new
empty profile and the problem persists and if reproducible at will.
2) Unfortunately I'm no longer able to to reproduce this problem when
using the example I've created so I must agree that the problem might
be somewhere else and will try again to extract an example form my
original application.
3) I'm still not sure where to start looking on what might cause this
problem and any help on what might cause this message in FireBug might
help me.
Thank you,
Dieter
On Oct 16, 12:46 am, Sebo <
sebastianzart...@gmx.de> wrote:
> > I did not really understand how this bug relates to my problem but
> > nevertheless happy to hear that it has been solved
>
> What mattcoz is describing is unfortunately *not* what you (Dieter) are
> experiencing.
> Explanation: In the Firefox nightly builds starting back in September there
> was a bug, that caused the Script panel to always show "No JavaScript on
> this page" (see bug 689101<
https://bugzilla.mozilla.org/show_bug.cgi?id=689101>
> ).
> Though this just affected Firefox Aurora (9.0a2) and Nightly (10.0a1) and is
> unrelated to FF 7.0.1, so your problem is unfortunately not solved by the
> fix of bug 689101.
>
> It's quite often used to store templates because the script tag prevents the
> content from being rendered.
>
> Yes, the script tag prevents the code from being displayed, though I still
> wonder, why you put HTML code into a <script> tag. Sorry to say, but it
> looks to me like abusing the script tag, because as its name says, it should
> just contain scripts.
>
> Usually the templates are in one or more external html files and loaded on
> demand using an ajax call.
>
> Ok, but after that AJAX call you have the contents of that file in a
> variable. So why do you need to save it into a <script> tag?
>
> While I am not convinced of that method your problem could still be a bug in
> Firebug (or Firefox). So you should test your test case from above in a
> fresh Firefox profile and tell us, if the problem is gone. If yes, it might
> be some preference or a conflict with another extension. Please also read
> the steps described at I found a Firebug Bug!<
http://getfirebug.com/wiki/index.php/I_found_a_Firebug_Bug%21>.