From 5da68c33af7045d6002df56a8d049f97a7afada5 Mon Sep 17 00:00:00 2001 From: Vincent Sanders Date: Sat, 3 Nov 2018 10:54:06 +0000 Subject: add js console discussion --- developer-weekend/nov-2018.mdwn | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/developer-weekend/nov-2018.mdwn b/developer-weekend/nov-2018.mdwn index 3eb0d81..df96f27 100644 --- a/developer-weekend/nov-2018.mdwn +++ b/developer-weekend/nov-2018.mdwn @@ -62,7 +62,7 @@ kinnison described five things that needed to be done: * events from the core browser window to frontends -### Corewindow for browser window change requirements +## Corewindow for browser window change requirements Everything except browser window has been moved over to corewindow. @@ -90,6 +90,19 @@ So front ends will only know about scale for e.g. saying scale in the title bar. All the complexity will move to browser_window. (For now; we should be able to improve matters with the new layout engine.) +## Javascript console + +currently console output gets NSLOG under netsurf context at INFO which is a pile of pants. Daniel thinks js console should be property on browser window + +* window needs to propogate html content pointer into console object +* console should fire content message when logging +* browser window should consume content message (bubbling as required) +* browser window api extended to support reading and clearing console and injecting js commands to run + +subsequently add interface to frontends, possibly core window + + + Activity ======== -- cgit v1.2.3