diff options
authorVincent Sanders <>2018-11-03 10:54:06 +0000
committerVincent Sanders <>2018-11-03 10:54:06 +0000
commit5da68c33af7045d6002df56a8d049f97a7afada5 (patch)
parent5ca8878a0feac4636c2f5e2abc3cfa304330861b (diff)
add js console discussion
1 files changed, 14 insertions, 1 deletions
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