Re: [Vimprobable-users] RFC: Added support for buffers
Vimprobable is a lean web browser optimised for full keyboard control
Brought to you by:
hanness
From: Hannes S. <ha...@yl...> - 2015-02-19 21:07:43
|
On Thu, 19 Feb 2015 10:54:02 +0800, Morgan Howe <mt...@gm...> wrote: > On Thu, Feb 19, 2015 at 2:39 AM, Hannes Schüller <ha...@yl...> > wrote: > > On Wed, 18 Feb 2015 01:17:26 -0500, Matthew Carter <m...@ah...> > > wrote: > >> I love that I can toggle what used to be tab specific features to a > >> set of buffers now. > > > > I'd say that's both the biggest strength and the biggest risk of > > this approach. If used right, i.e. for grouping pages of one > > website, this is extremely useful. If used wrong, i.e. to replace > > windows/tabs, this could lead to severe, unwanted breaches. > > Could you elaborate on this a bit? What kind of breaches are you > referring to? I mean situations where a user would inadvertently allow settings for a website he didn't intend. E.g. he would allow all cookies for a certain website and then call another site (which he doesn't want to have those privileges) in another buffer of the same window – *bam*, there are all those tracking cookies written to permanent storage! Similar things would apply to many settings. Things like this cannot be caught by technical means, of course. That is why I talked about *using* it right or wrong. > > Another thing to consider: How does the browser react if one of the > > buffers misbehaves, e.g. if the page in there won't stop executing > > some stupid script or something? Will it block all other buffers as > > well? Do I have to kill them all? > > This is a good point, and something I hadn't really thought about as I > hadn't yet run into this problem yet with vimprobable (unlike with > chrome :). I put together a simple test html with a javascript > infinite loop which, as somewhat expected, entirely hangs the browser. > However, this problem also exists with the current master so I don't > see that it's really anything specific to buffers aside from the > annoyance of losing multiple open pages rather than just one. Well, I'd say that's a major difference. If one page misbehaves, I don't mind killing and losing it. Pulling down other pages with it is really annoying. But, well, it could be another one of those things where people would just have to learn how to use it right, i.e. when to open a new window and when to open a new buffer. Hannes |