Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Firefox 5.0 support #11

Open
GoogleCodeExporter opened this issue Apr 10, 2015 · 7 comments
Open

Firefox 5.0 support #11

GoogleCodeExporter opened this issue Apr 10, 2015 · 7 comments

Comments

@GoogleCodeExporter
Copy link

Firefox update automatically to Firefox 5.0 and it is very difficult to down 
grade. Any support for firefox 5.0 in near future?


Original issue reported on code.google.com by [email protected] on 2 Jul 2011 at 5:49

@GoogleCodeExporter
Copy link
Author

Probably not. We've found that a lot of the apis that closure inspector uses 
are not very stable. Keeping it up to date took a lot of rewriting for each new 
firebug version, and we decided it wasn't worth the effort.

Original comment by Nicholas.J.Santos on 7 Jul 2011 at 6:09

@GoogleCodeExporter
Copy link
Author

Thank for your information. I tried downgrading, but the message is annoying

Original comment by [email protected] on 9 Jul 2011 at 10:35

@GoogleCodeExporter
Copy link
Author

Hello, how do you suggest to work then? are such features available in the 
chrome dev tools? how do you debug compiled js?

Original comment by [email protected] on 2 Aug 2011 at 8:01

@GoogleCodeExporter
Copy link
Author

Nicholas, any updates on this? Can you throw some light on teh future of 
Closure Inspector?

Thanks!
Pato

Original comment by [email protected] on 1 Sep 2011 at 2:57

@GoogleCodeExporter
Copy link
Author

Bump, bump, bump!! Has the Closure Inspector been abandoned, and if so, what 
does this mean for the future of the closure compiler? 

Original comment by [email protected] on 7 Sep 2011 at 10:38

@GoogleCodeExporter
Copy link
Author

 bump!! Has the Closure Inspector been abandoned, and if so, what does this mean for the future of the closure compiler? 

Original comment by [email protected] on 9 Sep 2011 at 7:07

@GoogleCodeExporter
Copy link
Author

Hi, I take it that the Closure Inspector is dead and working with older 
versions of Firefox is not practical. Surely, there must be occasions when 
Google developers need some debugging aid. Can anyone share how they debug 
closure apps without something like closure inspector? Are there other tools or 
anything in the works? 

Thanks

Original comment by [email protected] on 28 Oct 2011 at 11:16

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant