That stops execution and the callstack and environment are visible, but you can't see the user script code itself.
I've opened a bug at Mozilla, because I think this is a generic problem with the debugger not seeing sandboxed inline content scripts (for example that's everything that's run via executeScript and does not have a physical file representation inside the extension, including, but not limited to user scripts). Am 19. November 2017 18:25:57 MEZ schrieb Anthony Lieuallen <[email protected]>: >This is a limitation of A) the choices available and B) the time to >implement anything before Firefox 57 hit. > >I'd guess that inserting a `debugger;` statement might help you, but I >haven't tried it myself. > >-- >You received this message because you are subscribed to a topic in the >Google Groups "greasemonkey-users" group. >To unsubscribe from this topic, visit >https://groups.google.com/d/topic/greasemonkey-users/wIVnuHSLBuU/unsubscribe. >To unsubscribe from this group and all its topics, send an email to >[email protected]. >To post to this group, send email to >[email protected]. >Visit this group at https://groups.google.com/group/greasemonkey-users. >For more options, visit https://groups.google.com/d/optout. -- Gruß, Benedikt Bauer -- You received this message because you are subscribed to the Google Groups "greasemonkey-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/greasemonkey-users. For more options, visit https://groups.google.com/d/optout.
