From: Adam Thompson <firstname.lastname@example.org>
To: Karl Dahlke <email@example.com>
Subject: Re: [edbrowse-dev] It can be done, but is it worth it?
Date: Wed, 31 Mar 2021 18:31:20 +0100 [thread overview]
Message-ID: <YGSx6CeZxnMKm7Mh@toaster> (raw)
On Tue, Mar 30, 2021 at 10:41:58PM -0400, Karl Dahlke wrote:
> > There's part of me thinking to simply not have a master window
> Well there's no harm in having it, and no harm in using it for our deminimizing debugging stuff,
> which doesn't even go out to distribution.
> And that's kinda big, half a meg of source.
> And it sort of proves the concept if we choose to go further.
> Probably some actual functions can be shared safely, probably not classes.
> We have plenty of time to step back and think about it.
> For now it seems to be working pretty well.
> The most important thing is probably our find&fix, and a more complete DOM, etc.
Agreed, we need to try and fix what we know is broken for now and try and get more things working. However it's
definitely worth thinking about, particularly as sandboxing individual pages
appears to be an increasingly important part of browser design.
prev parent reply other threads:[~2021-03-31 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 0:43 Karl Dahlke
2021-03-29 16:53 ` Adam Thompson
2021-03-31 2:41 ` Karl Dahlke
2021-03-31 17:31 ` Adam Thompson [this message]
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).