This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Firefox with Netbeans integration | ||
---|---|---|---|
Product: | web | Reporter: | Christian Lenz <chrizzly> |
Component: | HTML Project | Assignee: | Tomas Mysik <tmysik> |
Status: | NEW --- | ||
Severity: | normal | CC: | terje7601 |
Priority: | P2 | ||
Version: | 7.4 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
Christian Lenz
2013-07-22 16:37:03 UTC
> maybe the same feature could be created for firefox?
That would be nice but realistically I do not think this is going to happen in a foreseeable future. It's a major undertaking because browser APIs are utterly different and maintaining and developing two plugins for two different platforms demands lots of resources. Sorry.
Taking over. It's a major undertaking because browser APIs are > utterly different and maintaining and developing two plugins for two > different platforms demands lots of resources. Sorry. There is a remotedebug.org (https://netbeans.org/bugzilla/show_bug.cgi?id=248312) and probably some analogues that are trying to unify browser debugging interfaces. Maybe it would be good to unify browser debugging using such tools? I see a huge gain of being compatible with all browsers. Actually we need more this https://github.com/auchenberg/remotedebug-firefox-bridge. Because remote debug uses Chrome remote debugging protocol, and this is a bridge to be able to debug with Firefox. https://github.com/campd/valence Take a look here. Joining valence team, and implementing support of those protocol could gave us ability to debug any browser we want. Isn't it a good idea? Another option is VorlonJS ( http://vorlonjs.com/ ). This seems to be the most browser-agnostic solution so far. |