794941 - Add a method of exposing chrome globals in the debugger UI

Status: RESOLVED DUPLICATE of bug 707302

(DevTools :: Debugger, defect, P2)

Comment 1

[Victor Porof [:vporof][:vp]]

Attachment: v1

Comment 2

[Victor Porof [:vporof][:vp]]

Note: the fact that tests still pass is an indicator that the crazy things I did are ok (at least for now), and any cleanup or prettification is due for 707302. That bug will make everything nice and pretty and sparkling and I already started working on it :)

Comment 3

[Victor Porof [:vporof][:vp]]

Attachment: v2

Now changing the "Filter Scripts" label to "Filter Chrome Globals" when appropriate.

Comment 4

[Victor Porof [:vporof][:vp]]

Attachment: v2.1

Apparently I messed up something in webconsole by accident, fact thoroughly shoved in my face by a try push. This fixes everything.

Comment 5

[Victor Porof [:vporof][:vp]]

Attachment: v2.2

Some other dumb stuff was happening.

Comment 6

[Victor Porof [:vporof][:vp]]

Attachment: v2.3

Rebased on top of 755661.

Comment 7

[Victor Porof [:vporof][:vp]]

Since a relatively non-negligible part of this patch (~30kb) is changed anyway in bug 707302, we could dupe this and qfold it with my work in that bug. This has the potential benefit of removing a review request from past's giant queue, but it'll postpone finishing the chrome debugger work for a few days 'till I finish 707302.

Your choice, past.

Comment 8

[Panos Astithas (he/him) [:past] (please ni?)]

Actually I think this patch isn't strictly required for the first cut of chrome debugging, since Debugger.Object.prototype.hostAnnotations won't be available to help us group module and documents separately. Maybe it would be better to make this bug depend on that, but feel free to do as you see fit.

Comment 9

[Victor Porof [:vporof][:vp]]

(In reply to Panos Astithas [:past] from comment #8)
> Actually I think this patch isn't strictly required for the first cut of
> chrome debugging, since Debugger.Object.prototype.hostAnnotations won't be
> available to help us group module and documents separately. Maybe it would
> be better to make this bug depend on that, but feel free to do as you see
> fit.

Well, I already started working on 707302 4 days ago and I based it on this bug, so making this depend on that would be paradoxical :)

I'll just dupe it since the functionality *is there*, but not pretty.

Comment 11

[Panos Astithas (he/him) [:past] (please ni?)]

(In reply to Victor Porof [:vp] from comment #9)
> (In reply to Panos Astithas [:past] from comment #8)
> > Actually I think this patch isn't strictly required for the first cut of
> > chrome debugging, since Debugger.Object.prototype.hostAnnotations won't be
> > available to help us group module and documents separately. Maybe it would
> > be better to make this bug depend on that, but feel free to do as you see
> > fit.
> 
> Well, I already started working on 707302 4 days ago and I based it on this
> bug, so making this depend on that would be paradoxical :)
> 
> I'll just dupe it since the functionality *is there*, but not pretty.

By "that" I meant the hostAnnotations bug, which I don't know if jimb has filed yet. Duping this is fine though.

Comment 12

[Panos Astithas (he/him) [:past] (please ni?)]

Comment on attachment 665612 [details] [diff] [review]
v2.3

Clearing the review for now, but do ping me when you have something ready in the other bug.

Comment 13

[Victor Porof [:vporof][:vp]]

(In reply to Panos Astithas [:past] from comment #12)
> Comment on attachment 665612 [details] [diff] [review]
> v2.3
> 
> Clearing the review for now, but do ping me when you have something ready in
> the other bug.

Sure thing.