* [Edbrowse-dev] console.log
@ 2017-02-01 20:18 Karl Dahlke
2017-02-01 23:04 ` Kevin Carhart
2017-02-21 18:34 ` [Edbrowse-dev] the cache and other pushes are very exciting Kevin Carhart
0 siblings, 2 replies; 3+ messages in thread
From: Karl Dahlke @ 2017-02-01 20:18 UTC (permalink / raw)
To: Edbrowse-dev
[-- Attachment #1: Type: text/plain, Size: 519 bytes --]
As more js starts to work, we get more console.log() messages. Example cartercenter.org. These just print, but could be annoying / unnecessary for the average user. What should we do?
Direct them to a file in the user's temp directory?
Direct them somewhere as per the user's config file?
Print them only at debug level 2 or higher?
I would opt for the latter - just not sure if it should be level 2 or 3.
This way they would be in the debug stream, if you were trying to figure something out.
Karl Dahlke
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-02-21 18:34 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-02-01 20:18 [Edbrowse-dev] console.log Karl Dahlke
2017-02-01 23:04 ` Kevin Carhart
2017-02-21 18:34 ` [Edbrowse-dev] the cache and other pushes are very exciting Kevin Carhart
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).