-
Notifications
You must be signed in to change notification settings - Fork 9
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
Analyze extensions performance impact for Firefox #26
Labels
Comments
On today's Add-ons Show and Tell we discussed this topic. Folks are positive about that. Hope that Importance for the Long Tasks API for Firefox will be changed. Waiting for @digitarald opinion about that. |
Trying to figure out (#28) possible usage of js-self-profiling API in case it will be implemented sooner. Bugzilla ticket |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The purpose of the project improving speed on a web. All results we were gathering related only to Chromium mostly. We’d like to extend results and see extensions (Add-ons) influence for Firefox users.
Some part of work was already done.
We are able to install add-ons using [Puppeteer(https://github.com/GoogleChrome/puppeteer).
Thanks for the help to extend API for web-ext repo to @aslushnikov @rpl @Rob--W.
More info can be found puppeteer/puppeteer#4162 and puppeteer/puppeteer#4162
Next step - use performance API which isn’t implemented yet in Firefox.
Related bugtracking issues:
All experiments are stored separate branch - https://github.com/treosh/exthouse/tree/firefox-experimental
The text was updated successfully, but these errors were encountered: