> Profiles are about separating Settings and user history, not for security isolation.
Where does it say that? Using profiles is currently like using different browsers altogether. How does that preclude security isolation? All that aside, how did you reach the conclusion if you read what I wrote? I was talking about a single unified mechanism to consolidate the various types of isolations, security or not, in an easily understandablr manner. There are also some very annoying papercuts that I believe will be solved with that.
> If you want to do that use the OS?
> Why should the browser implement a window manager, when the window manager already exists?
If you haven't noticed, the browser has grown in the past quarter of a century into a full-fledged OS-level platform with a complex GUI, a few dozen technologies, equally numerous APIs, a decent sandbox and an entire VM to run applications written in any of a few dozen programming languages. It's easier to write a small OS compared to a small browser. Implementing window managers inside a browser is not very hard or unusual. Some browsers do it in their main UI too. I was suggesting an extension of that concept. If it can improve the UX of a browser, why insist on gatekeeping it to the OS window manager?
> What stops you from putting two tabs side-by-side right now?
Where have you ever seen that done satisfactorily? Forget the numerous bars and panels all over the place that take up so much space. When have you ever been able to share information seamlessly like in a single window? It's so frustrating that it's a joke as a solution.
> You know, that you can put the menubar into the OS panel?
On which platform? How many WMs/DEs you know offer that facility? Unlike on MacOS where you can do that, window managers have a few dozen menu bars that aren't even compatible with each other. How many OS panels will each browser have to integrate with? Here instead, I'm suggesting the use of a technology that's already there - the web engine. In fact, that's how most browsers implement their main UI already. But it's not quite well integrated with the engine, at least in Firefox. My suggestion was to remove that limitation. You're objecting to something that's already there.
If you need something to be upset about browsers, there are plenty of egregious changes being pushed down the throats of the users. In contrast, I wasn't suggesting anything that the user has to accept without questions. It's also something that can be done with the building blocks already available. In fact, the changes you object to are already being partially implemented by many projects and are well-received by users as far as I can see. If we are this cynical about trying out great ideas from other platforms, what sort of progress are we expecting anyway?