590
edits
Comrade693 (talk | contribs) (→Potential Integration Issues: Added Issue 160) |
Comrade693 (talk | contribs) (→Potential Integration Issues: Added Issue 194; Fixed typo in Issue 160 title.) |
||
| Line 10: | Line 10: | ||
I feel that if we are targeting this to web developers, the errors in chrome won't be an issue since those are not displayed by default. However, if we expand the target group to Extension Developers, this will be a serious issue. There are easily over 50 strict warnings with startup alone, so it will be next to impossible for extension authors to find their own strict warnings. | I feel that if we are targeting this to web developers, the errors in chrome won't be an issue since those are not displayed by default. However, if we expand the target group to Extension Developers, this will be a serious issue. There are easily over 50 strict warnings with startup alone, so it will be next to impossible for extension authors to find their own strict warnings. | ||
===[http://code.google.com/p/fbug/issues/detail?id=160&can=4&q= Issue 160 - Firebug lacks | ===[http://code.google.com/p/fbug/issues/detail?id=160&can=4&q= Issue 160 - Firebug lacks full chrome under FreeBSD (and probably any platform except Darwin, Linux, linux-gnu, and WINNT)]=== | ||
'''Status:''' Researching. | '''Status:''' Researching. | ||
'''Disucssion:''' Reporter posted a fix that I need to investigate more. | '''Disucssion:''' Reporter posted a fix that I need to investigate more. | ||
===[http://code.google.com/p/fbug/issues/detail?id=194&can=4&q= Issue 194 - Firebug should be able to inspect chrome]=== | |||
'''Status:''' Researching. | |||
'''Disucssion:''' | |||
==Fixed Issues== | ==Fixed Issues== | ||
edits