Skip to main content
Notice removed Draw attention by CommunityBot
Bounty Ended with no winning answer by CommunityBot
Notice added Draw attention by canon
Bounty Started worth 200 reputation by canon
Notice removed Draw attention by CommunityBot
Bounty Ended with no winning answer by CommunityBot
Notice added Draw attention by T.J. Crowder
Bounty Started worth 400 reputation by T.J. Crowder
Notice removed Draw attention by KyleMitStaffMod
Bounty Ended with T.J. Crowder's answer chosen by KyleMitStaffMod
Notice added Draw attention by KyleMitStaffMod
Bounty Started worth 100 reputation by KyleMitStaffMod
Notice removed Draw attention by CommunityBot
Bounty Ended with no winning answer by CommunityBot
Notice added Draw attention by T.J. Crowder
Bounty Started worth 200 reputation by T.J. Crowder
Notice removed Draw attention by CommunityBot
Bounty Ended with no winning answer by CommunityBot
Notice added Draw attention by canon
Bounty Started worth 100 reputation by canon
Notice removed Draw attention by CommunityBot
Bounty Ended with no winning answer by CommunityBot
Notice added Draw attention by T.J. Crowder
Bounty Started worth 100 reputation by T.J. Crowder
added 65 characters in body
Source Link
Scimonster
  • 14.7k
  • 4
  • 36
  • 67

Currently, to see console.log() entries from StackSnippets, you need to open your browser console, and make sure it's recording from frames. Things could be a lot simpler if you would add a console to the snippets. Maybe something at the bottom of the snippet.

This could be done by overwriting the default console.log function with a custom one that both writes to the browser console (keep a reference to the original function), and also writes to the snippet's console.

EDIT:
And perhaps also show errors thrown in this console.

Currently, to see console.log() entries from StackSnippets, you need to open your browser console, and make sure it's recording from frames. Things could be a lot simpler if you would add a console to the snippets. Maybe something at the bottom of the snippet.

This could be done by overwriting the default console.log function with a custom one that both writes to the browser console (keep a reference to the original function), and also writes to the snippet's console.

Currently, to see console.log() entries from StackSnippets, you need to open your browser console, and make sure it's recording from frames. Things could be a lot simpler if you would add a console to the snippets. Maybe something at the bottom of the snippet.

This could be done by overwriting the default console.log function with a custom one that both writes to the browser console (keep a reference to the original function), and also writes to the snippet's console.

EDIT:
And perhaps also show errors thrown in this console.