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

WIP: Support for multiple iframes #182

Merged
merged 4 commits into from Aug 5, 2014
Merged

WIP: Support for multiple iframes #182

merged 4 commits into from Aug 5, 2014

Conversation

teddyzeenny
Copy link
Contributor

Adds the ability to choose an iframe from a dropdown in case an Ember application was detected in more than one window / iframe.

  • Chrome support
  • Firefox support

I need some help with testing this in real life cases (only Chrome works currently).

@stefanpenner
Copy link
Member

👍

rpl added a commit to rpl/ember-inspector that referenced this pull request Jul 29, 2014
This commit introduces a complete refactoring/cleanup of the Firefox
version, it supports Ember apps embedded into iframes on Firefox 
(Ember libraries detection and Devtool panel connection) and it has 
an optional tomster icon in the locationbar.

The tomster icon can be enabled/disabled from the addon preferences, 
and it will be visible when an Ember app is detected in the tab or 
in an iframe inside the tab).

Requirements:
- Firefox >= 30.0 (needed for the "evalInWindow" method used in content-script)

Tested on:
- http://jsfiddle.net/9zHj9/1/

to be merged into emberjs#182
@rpl
Copy link
Contributor

rpl commented Jul 29, 2014

@teddyzeenny This is really awesome!

I've just pushed the changes needed on Firefox firefox side and opened #187 to add more info about the changes.

@teddyzeenny
Copy link
Contributor Author

Wow :) Thank you @rpl for this amazing work!!

Everything seems to be great except I can't run file:// anymore. Any idea what could be the reason?

@rpl
Copy link
Contributor

rpl commented Aug 5, 2014

@teddyzeenny It's my pleasure.

I just pushed as #189 a very small fix, which enables "file://" urls on the page-mod created by the Firefox addon.

@teddyzeenny
Copy link
Contributor Author

@rpl merged :)

@teddyzeenny
Copy link
Contributor Author

The Firefox tomster is now better than the Chrome one (detects iframes and has a button to open the inspector).

teddyzeenny and others added 4 commits August 5, 2014 15:25
This commit introduces a complete refactoring/cleanup of the Firefox
version, it supports Ember apps embedded into iframes on Firefox
(Ember libraries detection and Devtool panel connection) and it has
an optional tomster icon in the locationbar.

The tomster icon can be enabled/disabled from the addon preferences,
and it will be visible when an Ember app is detected in the tab or
in an iframe inside the tab).

Requirements:
- Firefox >= 30.0 (needed for the "evalInWindow" method used in content-script)

Tested on:
- http://jsfiddle.net/9zHj9/1/

to be merged into #182
teddyzeenny added a commit that referenced this pull request Aug 5, 2014
Support for multiple iframes
@teddyzeenny teddyzeenny merged commit e7cc751 into master Aug 5, 2014
@stefanpenner
Copy link
Member

wooooo!

@teddyzeenny teddyzeenny deleted the iframes branch August 8, 2014 12:48
@mansona
Copy link
Member

mansona commented Aug 20, 2014

Hey guys, awesome work! I've been waiting for this one for ages 👍

Just have a question: i'm right in thinking this made it into the 1.4.0 verison of the chrome plugin right? I'm trying to get this to work on an iframe and I don't know how to point it at the frame

@teddyzeenny
Copy link
Contributor Author

Yes this is in 1.4.0. There should be a dropdown on the bottom left that lists the iframes that contain an Ember app.

screen shot 2014-08-20 at 1 57 07 pm

@mansona
Copy link
Member

mansona commented Aug 20, 2014

So we don't get that far... does the frame need to be there on page load? We add the frame in after a button push and that might be the cause of this.

Maybe i create an issue so we can discuss it there?

@teddyzeenny
Copy link
Contributor Author

This line is supposed to catch the new iframe. It might be related to the iframe URL or the iframe is sandboxed...

Would be great if you can reproduce this online.
Let's open a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants