> Finally, I guess that one more source of confusion about this is that when
#Firebug lite for chrome install
> cannot install one, you can also use the bookmarklet: > Again, we recommend using a local web server. > this problem, we could release it in our site in the beta channel (but first > manually approved by Google in order to be in the Chrome Web Store.
> Also, extensions that uses "file:///" in the mafinest.json need to be > us to execute scripts in it, which means we cannot load Firebug Lite: > We could add "file:///" to the mafinest.json, but there's a bug preventing > not all designers use local web servers. > files is related to design things like tweaking CSS, and I also presume that > At the same time, I presume that the most common case for using "file:///" > We recommend using a local web server, which the most secure and error proof I'll add a message box informing what is happening. There is no message indicating that Firebug Lite could not be loaded. But if you don't want or cannot install one, you can also use the bookmarklet:įinally, I guess that one more source of confusion about this is that when you click at the Firebug Lite extension button, nothing happens.
To avoid this problem, we could release it in our site in the beta channel (but first we need that bug to be fixed):Īgain, we recommend using a local web server. We could add "file:///" to the mafinest.json, but there's a bug preventing us to execute scripts in it, which means we cannot load Firebug Lite:Īlso, extensions that uses "file:///" in the mafinest.json need to be manually approved by Google in order to be in the Chrome Web Store. We recommend using a local web server, which the most secure and error proof solution.Īt the same time, I presume that the most common case for using "file:///" files is related to design things like tweaking CSS, and I also presume that not all designers use local web servers. For security reasons, extensions are not allowed to run in pages loaded via "file:///" protocol: