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

Mark as e10s compatible #8030

Closed
janodvarko opened this Issue Jun 21, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@janodvarko
Member

janodvarko commented Jun 21, 2016

Firebug xpi should be marked as e10s compatible. Firebug itself doesn't work with e10s, but migration UI that helps users to shift to built-in Firefox DevTools must work.

Honza

@janodvarko janodvarko self-assigned this Jun 21, 2016

janodvarko added a commit that referenced this issue Jun 21, 2016

@Chealer

This comment has been minimized.

Show comment
Hide comment
@Chealer

Chealer Oct 11, 2016

Thank you Honza, for your work on this issue and on Firebug in general.

I could not understand the 2.0.18 release notes, which contain:

It does not mean that Firebug itself supports multi-process browser.

I suggest to replace that with:

When opened in a multi-process Firefox, Firebug's tools cannot be used. Firebug will then only assist the user with migration to Firefox's built-in tools.

Chealer commented Oct 11, 2016

Thank you Honza, for your work on this issue and on Firebug in general.

I could not understand the 2.0.18 release notes, which contain:

It does not mean that Firebug itself supports multi-process browser.

I suggest to replace that with:

When opened in a multi-process Firefox, Firebug's tools cannot be used. Firebug will then only assist the user with migration to Firefox's built-in tools.

@janodvarko

This comment has been minimized.

Show comment
Hide comment
@janodvarko

janodvarko Oct 12, 2016

Member

@Chealer: done, thanks!

Honza

Member

janodvarko commented Oct 12, 2016

@Chealer: done, thanks!

Honza

@janodvarko janodvarko closed this Oct 12, 2016

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