Hi,
I went a bit further. Each window/tab should be locked to an origin,
and it should have an origin-private browser profile, and process
isolation.
I already produced a proof of concept using surf for webkit1, but
webkit2 doesn't have the necessary navigation hooks in its API.
https://github.com/legitparty/surf-isolated
I haven't touched it in some time, but it is more of a proof of
concept. The documentation is only in my commit messages, and some
prior mailing list posts here which summarize. I am mostly now putting
my faith in Mozilla and their partnership with Tor, and their tab
isolation they are working on. My proposal is far more strict, and has
a bit more user friction, so maybe Mozilla can come up with a model
that is less friction, and other browsers can adopt what they get
working.
But seeing how I did it could give you ideas on how to do what you two
have been talking about.
Ben
On Sat, Apr 15, 2017 at 9:59 AM, <ssd_AT_mailless.org> wrote:
> * hiro 2017-04-14 17:11
>> personally i think tabs are stupid. there should be one url and title
>> per process.
>
> this!
>
> it's on my todo for long time now to come up with a clean and simple way
> to deal with stateful surf sessions (session being an arbitrary number,
> N, of current urls (and possibly histories)).
>
> the obvious approach is to have history and current url per surf window;
> but a worthwhile one could be to have a single surf window with N
> “buffers” -- one active and N-1 inactive at a time.
>
> what I'm trying to say is that i'd appreciate if the code is not tied
> to tabbed, but rather generally applicable to a collection of surf
> processes or something.
>
> cheers
> --s
>
Received on Sat Apr 15 2017 - 22:37:58 CEST