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

Host DevTools on own permalink page via <iframe> #5

Open
auchenberg opened this issue Jan 21, 2016 · 5 comments
Open

Host DevTools on own permalink page via <iframe> #5

auchenberg opened this issue Jan 21, 2016 · 5 comments

Comments

@auchenberg
Copy link
Owner

  • Build session permalink page with some branding
  • Load Hosted DevTools via <iframe> from AppSpot
@kzahel
Copy link

kzahel commented Mar 3, 2017

I'd love to be able to load specific devtools revisions (or any at all) in a http(s) URL. I tried using https://github.com/ChromeDevTools/devtools-frontend but the package.json did not have any scripts that seemed relevant to building the static html/css/js assets to be able to host a devtools instance. Any tips?

@auchenberg
Copy link
Owner Author

Chrome is providing a cloud hosted front-end on AppSpot, so that would be ideal. Wanna try to give it a spin @kzahel ?

@kzahel
Copy link

kzahel commented Mar 3, 2017

Definitely! I saw that it was using appcache to download/store the assets. Would I just have it do that again and copy the URL format?

@kzahel
Copy link

kzahel commented Mar 3, 2017

Hmm I found a URL that seems to work (https://chrome-devtools-frontend.appspot.com/serve_file/@d19c087b9bfdf76a8af91e2f0a0e791bf2ffcafa/inspector.html)

But it seems it doesn't include emulated mobile devices module?

Application Cache Error event: Resource fetch failed (404) https://chrome-devtools-frontend.appspot.com/serve_file/@d19c087b9bfdf76a8af91e2f0a0e791bf2ffcafa/emulated_devices/emulated_devices_module.js

@kzahel
Copy link

kzahel commented Mar 3, 2017

I tried running scripts/compile_frontend.py but it wanted v8 and other things checked out so I compiled Chrome. Now I have a compiled frontend in my build output folder. However there is no AppCache manifest created. Is the script mentioned at https://groups.google.com/a/chromium.org/d/msg/devtools-reviews/3izWlIsoIl8/v-rhJ6upkNYJ (one that injects manifest url into inspector.html) somewhere in the chromium repository? or is that somewhere else?

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

2 participants