Handle the debugger detaching in chrome extension
In accordance with the Debugger DevTools API, there is no debugger detach event. Can I catch the event for detaching the debugger when the user clicking "cancel" e.g.?
Sample code for attach:
chrome.debugger.attach(
{
tabId: tabId
},
'1.3',
() => {
chrome.debugger.sendCommand(
{
tabId: tabId
},
'Debugger.enable',
{},
result => {
// ...
}
);
}
);
google-chrome-extension google-chrome-devtools chrome-debugging asked Nov 12 at 11:38
wrager
3651216
add a comment |
In accordance with the Debugger DevTools API, there is no debugger detach event. Can I catch the event for detaching the debugger when the user clicking "cancel" e.g.?
Sample code for attach:
chrome.debugger.attach(
{
tabId: tabId
},
'1.3',
() => {
chrome.debugger.sendCommand(
{
tabId: tabId
},
'Debugger.enable',
{},
result => {
// ...
}
);
}
);
asked Nov 12 at 11:38
wrager
3651216
1
I don't get the question.chrome.debugger.onDetachis a thing. How is it not what you want?
– Xan
Nov 14 at 11:20
Oh, I see, you're talking about debugger feature within the devtools disabling.
– Xan
Nov 14 at 11:21
@Xan No, I am talking about detaching debugger that was attached by chrome.debugger.attach, not the debugger feature. That is exactly what I looking for! Please post the answer and I will approve it.
– wrager
Nov 14 at 11:41
add a comment |
In accordance with the Debugger DevTools API, there is no debugger detach event. Can I catch the event for detaching the debugger when the user clicking "cancel" e.g.?
Sample code for attach:
chrome.debugger.attach(
{
tabId: tabId
},
'1.3',
() => {
chrome.debugger.sendCommand(
{
tabId: tabId
},
'Debugger.enable',
{},
result => {
// ...
}
);
}
);
asked Nov 12 at 11:38
wrager
3651216
In accordance with the Debugger DevTools API, there is no debugger detach event. Can I catch the event for detaching the debugger when the user clicking "cancel" e.g.?
Sample code for attach:
chrome.debugger.attach(
{
tabId: tabId
},
'1.3',
() => {
chrome.debugger.sendCommand(
{
tabId: tabId
},
'Debugger.enable',
{},
result => {
// ...
}
);
}
);
asked Nov 12 at 11:38
wrager
3651216
asked Nov 12 at 11:38
wrager
3651216
edited Nov 13 at 14:58
asked Nov 12 at 11:38
wrager
3651216
asked Nov 12 at 11:38
wrager
3651216
asked Nov 12 at 11:38
wrager
3651216
3651216
1
I don't get the question.chrome.debugger.onDetachis a thing. How is it not what you want?
– Xan
Nov 14 at 11:20
Oh, I see, you're talking about debugger feature within the devtools disabling.
– Xan
Nov 14 at 11:21
@Xan No, I am talking about detaching debugger that was attached by chrome.debugger.attach, not the debugger feature. That is exactly what I looking for! Please post the answer and I will approve it.
– wrager
Nov 14 at 11:41
add a comment |
1
I don't get the question.chrome.debugger.onDetachis a thing. How is it not what you want?
– Xan
Nov 14 at 11:20
Oh, I see, you're talking about debugger feature within the devtools disabling.
– Xan
Nov 14 at 11:21
@Xan No, I am talking about detaching debugger that was attached by chrome.debugger.attach, not the debugger feature. That is exactly what I looking for! Please post the answer and I will approve it.
– wrager
Nov 14 at 11:41
1
1
I don't get the question.
chrome.debugger.onDetach is a thing. How is it not what you want?– Xan
Nov 14 at 11:20
I don't get the question.
chrome.debugger.onDetach is a thing. How is it not what you want?– Xan
Nov 14 at 11:20
Oh, I see, you're talking about debugger feature within the devtools disabling.
– Xan
Nov 14 at 11:21
Oh, I see, you're talking about debugger feature within the devtools disabling.
– Xan
Nov 14 at 11:21
@Xan No, I am talking about detaching debugger that was attached by chrome.debugger.attach, not the debugger feature. That is exactly what I looking for! Please post the answer and I will approve it.
– wrager
Nov 14 at 11:41
@Xan No, I am talking about detaching debugger that was attached by chrome.debugger.attach, not the debugger feature. That is exactly what I looking for! Please post the answer and I will approve it.
– wrager
Nov 14 at 11:41
add a comment |
2 Answers
2
active
oldest
votes
If you're looking to catch your debugger connection being closed (as opposed to an event happening within that connection), there is a chrome.debugger.onDetach event provided by the API.
answered Nov 14 at 11:43
Xan
53.1k10101128
add a comment |
I made a workaround that suits me: setInterval with try/catch some debugger command.
const intervalId = setInterval(async () => {
try {
// await send 'Debugger.setBreakpointsActive' with active=true
} catch (error) {
clearInterval(intervalId);
onDetach();
}
}, 500);
answered Nov 12 at 13:54
wrager
3651216
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53261379%2fhandle-the-debugger-detaching-in-chrome-extension%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you're looking to catch your debugger connection being closed (as opposed to an event happening within that connection), there is a chrome.debugger.onDetach event provided by the API.
answered Nov 14 at 11:43
Xan
53.1k10101128
add a comment |
If you're looking to catch your debugger connection being closed (as opposed to an event happening within that connection), there is a chrome.debugger.onDetach event provided by the API.
answered Nov 14 at 11:43
Xan
53.1k10101128
add a comment |
If you're looking to catch your debugger connection being closed (as opposed to an event happening within that connection), there is a chrome.debugger.onDetach event provided by the API.
answered Nov 14 at 11:43
Xan
53.1k10101128
If you're looking to catch your debugger connection being closed (as opposed to an event happening within that connection), there is a chrome.debugger.onDetach event provided by the API.
answered Nov 14 at 11:43
Xan
53.1k10101128
answered Nov 14 at 11:43
Xan
53.1k10101128
answered Nov 14 at 11:43
Xan
53.1k10101128
answered Nov 14 at 11:43
Xan
53.1k10101128
53.1k10101128
add a comment |
add a comment |
I made a workaround that suits me: setInterval with try/catch some debugger command.
const intervalId = setInterval(async () => {
try {
// await send 'Debugger.setBreakpointsActive' with active=true
} catch (error) {
clearInterval(intervalId);
onDetach();
}
}, 500);
answered Nov 12 at 13:54
wrager
3651216
add a comment |
I made a workaround that suits me: setInterval with try/catch some debugger command.
const intervalId = setInterval(async () => {
try {
// await send 'Debugger.setBreakpointsActive' with active=true
} catch (error) {
clearInterval(intervalId);
onDetach();
}
}, 500);
answered Nov 12 at 13:54
wrager
3651216
add a comment |
I made a workaround that suits me: setInterval with try/catch some debugger command.
const intervalId = setInterval(async () => {
try {
// await send 'Debugger.setBreakpointsActive' with active=true
} catch (error) {
clearInterval(intervalId);
onDetach();
}
}, 500);
answered Nov 12 at 13:54
wrager
3651216
I made a workaround that suits me: setInterval with try/catch some debugger command.
const intervalId = setInterval(async () => {
try {
// await send 'Debugger.setBreakpointsActive' with active=true
} catch (error) {
clearInterval(intervalId);
onDetach();
}
}, 500);
answered Nov 12 at 13:54
wrager
3651216
answered Nov 12 at 13:54
wrager
3651216
answered Nov 12 at 13:54
wrager
3651216
answered Nov 12 at 13:54
wrager
3651216
3651216
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53261379%2fhandle-the-debugger-detaching-in-chrome-extension%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
I don't get the question.
chrome.debugger.onDetachis a thing. How is it not what you want?– Xan
Nov 14 at 11:20
Oh, I see, you're talking about debugger feature within the devtools disabling.
– Xan
Nov 14 at 11:21
@Xan No, I am talking about detaching debugger that was attached by chrome.debugger.attach, not the debugger feature. That is exactly what I looking for! Please post the answer and I will approve it.
– wrager
Nov 14 at 11:41