This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 972
Added ability to inspect extension background page #7880
Labels
Milestone
Comments
bridiver
added a commit
that referenced
this issue
Mar 25, 2017
fix #7880 requires brave/muon@42b9c96 note: url will not properly reset until #7894 is fixed
3 tasks
bridiver
added a commit
that referenced
this issue
Mar 25, 2017
bridiver
added a commit
that referenced
this issue
Mar 26, 2017
bridiver
added a commit
that referenced
this issue
Mar 26, 2017
QA is blocked on #7894. Cf: #7895 (comment) |
"url will not properly reset" issue is not critial? if it does not have influence on UX, I'll change the label. |
I removed that because I found another way to make it work, but either way it isn't a blocker for this, just a note
… On Mar 26, 2017, at 9:51 AM, Suguru Hirahara ***@***.***> wrote:
"url will not properly reset" issue is not critial? if it does not have influence on UX, I'll change the label.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
|
bsclifton
pushed a commit
that referenced
this issue
Mar 26, 2017
This was referenced Mar 28, 2017
alexwykoff
changed the title
Inspect Extension Background Page
Added ability to inspect extension background page
Mar 30, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Test plan
#7895 (comment)
Did you search for similar issues before submitting this one?
Yes
Describe the issue you encountered:
I would like to open an instance of the developer tools, and have it be connected the the background page of a particular extension.
Platform (Win7, 8, 10? macOS? Linux distro?):
Desktop
Is this an issue in the currently released version?
Yes
Screenshot if needed:
From chrome's about:extensions page:
The text was updated successfully, but these errors were encountered: