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 support #28

Open
14 tasks
notetiene opened this issue Apr 19, 2017 · 9 comments
Open
14 tasks

Firefox support #28

notetiene opened this issue Apr 19, 2017 · 9 comments

Comments

@notetiene
Copy link
Contributor

notetiene commented Apr 19, 2017

I'm currently trying to implement the Firefox backend. However, given the major differences between the Firefox remote debugging protocol and the Chrome one, I think it could be nice to include a todo list here.

  • Implement the Firefox Remote Debugger Protocol Backend
    • Implement the protocol API (we might look at this).
    • Implement a function to query tabs information
    • Since Firefox doesn't have a per tab protocol should we use only one process for all tabs? Also each times we make a new connection, Firefox display a prompt to accept remote debugging.
    • Implement the evaluation function
    • Implement the completion function
    • Implement the debugger functions
      - [ ] Implement the breakpoints functions
      • Implement the resume function
      • Implement the step-into function
      • Implement the step-out function
      • Implement the step-over function
      • Implement the continue function
          - [ ] Implement pausing on exceptions and get them
    • Implement the property inspector
    • Sync the console logs

That's all for now.

@NicolasPetton
Copy link
Owner

NicolasPetton commented Apr 26, 2017

@notetiene do you want to push your commits somewhere so I could have a look?

@NicolasPetton
Copy link
Owner

@notetiene also, since until now all backends are chrome/v8 centric, there might be refactorings to do in Indium to make it easier to implement. If that's the case, don't hesitate to tell me, I'll help the best way I can.

@notetiene
Copy link
Contributor Author

Thanks for you comments.

I'm really interested in supporting Firefox. Sadly, I don't have much time for the following 2 weeks and my current commits only cover common variables I found between the two backends.

I'll notify you when I start working on it. 😄

@NicolasPetton
Copy link
Owner

Mozilla is apparently thinking about adding support for the CDP, in which case we wouldn't have to implement a specific backend for it.

@notetiene
Copy link
Contributor Author

@NicolasPetton That would be great! Sadly, I'm not able to see any news concerning CDP in Firefox. Is it an official project?

@NicolasPetton
Copy link
Owner

NicolasPetton commented Jan 10, 2018 via email

@dakra
Copy link

dakra commented Jan 11, 2018

That would be great. I found a few issues on their bugtracker but non sound like it's coming anytime soon :(
https://bugzilla.mozilla.org/show_bug.cgi?id=1316741
Most recent one seems to be https://bugzilla.mozilla.org/show_bug.cgi?id=1391465

@nbfalcon
Copy link

This blog post by mozilla talks about how they are implementing CDP for the sake of puppeteer.js support.

@NicolasPetton
Copy link
Owner

I've been following their progress about this for a while, but I missed this post. @nbfalcon thanks for the link!

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

4 participants