Go to file
Daniel Silverstone 6fc2666d07
Allow contents to indicate if they believe they may not be secure.
HTML contents reference many other objects.  The browser window
needs to know if any of them may not be secure, in which case it
needs to report that in its page state.  If other content types
might refer to sub-contents, they will need to define the callback
too.

Signed-off-by: Daniel Silverstone <dsilvers@digital-scurf.org>
2019-12-01 15:49:08 +00:00
content Allow contents to indicate if they believe they may not be secure. 2019-12-01 15:49:08 +00:00
desktop Allow contents to indicate if they believe they may not be secure. 2019-12-01 15:49:08 +00:00
docs update ingored directories in gource helper 2019-09-29 22:14:05 +01:00
frontends fix win32 frontend to allow setting unicode titles 2019-12-01 11:27:21 +00:00
include/netsurf browser_window: Add basic page info state and SSL accessors 2019-12-01 15:01:24 +00:00
resources remove spurious whitespace in fetch error pages 2019-11-04 11:47:30 +00:00
test use faster loader for yaml in test parsing 2019-11-30 15:41:20 +00:00
utils fix compatability macros setup for NetBSD 2019-11-13 17:58:06 +00:00
.clang-format update clang format style for version 7 2019-10-10 18:22:23 +01:00
.gitattributes add attributes file to stop .gitignore being exported 2013-04-19 21:27:45 +01:00
.gitignore make framebuffer use the language environment for the UI resources 2019-02-17 00:11:27 +00:00
COPYING Clarify licensing arrangements 2007-08-09 15:32:39 +00:00
Makefile make the use of libutf8proc coditional 2019-10-03 00:28:08 +01:00
Makefile.config.example Dukky: Add and utilise a jserrors category 2019-08-02 10:12:45 +01:00
Makefile.defaults Logging: Include VERBOSE in the binary by default. 2019-11-30 20:14:12 +00:00
README Fix to point at current build documentaion. 2014-07-22 15:36:36 +01:00

--------------------------------------------------------------------------------
  NetSurf README
--------------------------------------------------------------------------------

  This document should help point you at various useful bits of information.


  Building NetSurf
==================
  
  Read the QUICK-START document in the Docs/ directory for instructions.


  Creating a new port
=====================

  Look at the existing front ends for example implementations.  The framebuffer
  front end is simplest and most self-contained.  Also, you can contact the
  developers for help:

      http://www.netsurf-browser.org/contact/

  Check out the developer documentation sources listed below too.


  Further documentation
=======================

  The Developer section of the web site has loads of info to get you started:

      http://www.netsurf-browser.org/developers/

  General documentation on how NetSurf's code works can be found on the
  development wiki:

      http://wiki.netsurf-browser.org/Documentation/

  The code style guide is here:

      http://www.netsurf-browser.org/developers/StyleGuide.pdf