Add ability to inspect iframes

[btford]

Currently, sites like Punker do not work with Batarang because iframes are not instrumented.

[petebacondarwin]

+1

[tilgovi]

Any batarang contributors able to provide any helpful information to get me started with tackling this?

[SebC99]

+1

[Catincan]

Bounty of $50.00 is available on this issue: https://www.catincan.com/bounty/https-github-com-angular-angularjs-batarang-issues-14

[nickradford]

Any progress being made with this?

[veroniquepelletier]

+1

[ivandotv]

+1

[jakefreeberg]

+1

[crstffr]

+1

[nicklasnygren]

+1

[Justin-Credible]

+1 Would be useful for mobile apps when using Apache Ripple during development (it uses an iframe as well).

[GVisconti84]

+1

[gngeorgiev]

+1

[milushov]

:+1:

[steve8708]

+1

[slavkomae]

+1

[AlexNeyman]

+1

[cleargif]

+1

[abraman1]

:+1:

[lallmon]

lol @abraman1

This would be mega-valuable so :+1:

[Facius]

+1

[SomeKittens]

@Facius GitHub gave us the ability to 👍 things, don't add superfluous comments

[Roachsec]

Need this for my thesis, building a chrome extension with angular is really tedious the way things are now. If anyone knows of alternatives I'd love to hear it.

[gkalpak]

@RogierVelde, what does this have to do with building extensions using Angular ?

[Roachsec]

I inject an iframe on the page, can't inspect it like this. It needs data from the parent page so I can't inspect it in a separate window either. Being able to explore the scope, among other things, would accelerate development a lot.

[gkalpak]

So, you mean you can't use Batarang to debug an extension that injects an iframe. This is very different from "building a chrome extension with angular is really tedious the way things are now" :smiley:

Does anyone have any idea what is stopping Batarang from instrumenting iframes ?

[meekaah]

this is really needed... 👍

[mdenburger]

+1

[RyanF13]

+1

[madhu131313]

+1