Gitweb links:
...log
http://git.netsurf-browser.org/netsurf-wiki.git/shortlog/772bb03198f96ae821dc134eea72b05c2f248bfa
...commit
http://git.netsurf-browser.org/netsurf-wiki.git/commit/772bb03198f96ae821dc134eea72b05c2f248bfa
...tree
http://git.netsurf-browser.org/netsurf-wiki.git/tree/772bb03198f96ae821dc134eea72b05c2f248bfa
The branch, master has been updated
via 772bb03198f96ae821dc134eea72b05c2f248bfa (commit)
from 04df956c80fbed4d677b3ecad735ca4390b0ceb6 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commitdiff
http://git.netsurf-browser.org/netsurf-wiki.git/commit/?id=772bb03198f96ae821dc134eea72b05c2f248bfa
commit 772bb03198f96ae821dc134eea72b05c2f248bfa
Author: Daniel Silverstone <[email protected]>
Commit: Daniel Silverstone <[email protected]>
Plan
diff --git a/developer-weekend/dec-2019.mdwn b/developer-weekend/dec-2019.mdwn
index 4b09b14..0d9f7db 100644
--- a/developer-weekend/dec-2019.mdwn
+++ b/developer-weekend/dec-2019.mdwn
@@ -129,6 +129,36 @@ Vince
* Finished extended internet test badgering including full reorganisation of
the monkey-tests tree.
+Plan for page info
+==================
+
+1. We add to browser_window the concept of the currently displayed page info.
+2. That info is an enumeration of:
+ * UNKNOWN (nothing loaded?)
+ * INTERNAL (e.g. `about:` etc)
+ * INSECURE (e.g. `http://`)
+ * SECURE+PROBLEMS (e.g. `https://` but `http://` images, or badssl)
+ * SECURE (all is well)
+3. Whenever the currently displayed page changes, `browser_window` will send a
+ notification to the GUI, which will then be able to retrieve the current
+ state information.
+4. More detailed page information will be available through further APIs
+
+Then separately
+
+When the page information button is clicked, the GUI pops up a corewindow for
+it. This window will show information about the page's security, etc. Most of
+the information for this can be directly retrieved from the browser_window and
+as such, the corewindow will be initialised with the browser_window pointer.
+The GUI will be responsible for destroying the corewindow when the browser
+window is going away, and for notifying the corewindow when the browser window
+event indicating info-change occurs.
+
+This means that the corewindow is borrowing from the browser window, so we need
+to ensure that anything the browser window returns by pointer will remain safe
+for use even when navigation events occur.
+
+
Statement of work
=================
-----------------------------------------------------------------------
Summary of changes:
developer-weekend/dec-2019.mdwn | 30 ++++++++++++++++++++++++++++++
1 file changed, 30 insertions(+)
diff --git a/developer-weekend/dec-2019.mdwn b/developer-weekend/dec-2019.mdwn
index 4b09b14..0d9f7db 100644
--- a/developer-weekend/dec-2019.mdwn
+++ b/developer-weekend/dec-2019.mdwn
@@ -129,6 +129,36 @@ Vince
* Finished extended internet test badgering including full reorganisation of
the monkey-tests tree.
+Plan for page info
+==================
+
+1. We add to browser_window the concept of the currently displayed page info.
+2. That info is an enumeration of:
+ * UNKNOWN (nothing loaded?)
+ * INTERNAL (e.g. `about:` etc)
+ * INSECURE (e.g. `http://`)
+ * SECURE+PROBLEMS (e.g. `https://` but `http://` images, or badssl)
+ * SECURE (all is well)
+3. Whenever the currently displayed page changes, `browser_window` will send a
+ notification to the GUI, which will then be able to retrieve the current
+ state information.
+4. More detailed page information will be available through further APIs
+
+Then separately
+
+When the page information button is clicked, the GUI pops up a corewindow for
+it. This window will show information about the page's security, etc. Most of
+the information for this can be directly retrieved from the browser_window and
+as such, the corewindow will be initialised with the browser_window pointer.
+The GUI will be responsible for destroying the corewindow when the browser
+window is going away, and for notifying the corewindow when the browser window
+event indicating info-change occurs.
+
+This means that the corewindow is borrowing from the browser window, so we need
+to ensure that anything the browser window returns by pointer will remain safe
+for use even when navigation events occur.
+
+
Statement of work
=================
--
NetSurf Developer Wiki Backing Store
_______________________________________________
netsurf-commits mailing list
[email protected]
http://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/netsurf-commits-netsurf-browser.org
