Oxide should log messages to the console by default

[Chris Coulson]

We currently don't log any console.log() messages to the console by default, but instead require that applications implement WebView::javaScriptConsoleMessage. We could probably change this so that we log messages (for non-incognito webviews) if there are no slots connected to that signal.

[David Barth (dbarth)]

+1 !

On Fri, Jan 20, 2017 at 11:58 PM, Chris Coulson <email address hidden>
wrote:

> Public bug reported:
>
> We currently don't log any console.log() messages to the console by
> default, but instead require that applications implement
> WebView::javaScriptConsoleMessage. We could probably change this so that
> we log messages (for non-incognito webviews) if there are no slots
> connected to that signal.
>
> ** Affects: oxide
> Importance: Low
> Status: Triaged
>
> ** Changed in: oxide
> Importance: Undecided => Low
>
> ** Changed in: oxide
> Status: New => Triaged
>
> --
> You received this bug notification because you are a member of Ubuntu
> WebApps bug tracking, which is subscribed to Oxide.
> https://bugs.launchpad.net/bugs/1658231
>
> Title:
> Oxide should log messages to the console by default
>
> Status in Oxide:
> Triaged
>
> Bug description:
> We currently don't log any console.log() messages to the console by
> default, but instead require that applications implement
> WebView::javaScriptConsoleMessage. We could probably change this so
> that we log messages (for non-incognito webviews) if there are no
> slots connected to that signal.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/oxide/+bug/1658231/+subscriptions
>
> --
> Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
> More help : https://help.launchpad.net/ListHelp
>