PSA: Recent Split View changes

Some brief info:

This week Chromium removed the Split View flag that had existed in chrome://flags. That change was inherited by Brave and so no longer is at brave://flags either. These are experimental flags and never promised to stay.

To emphasize, this is not anything introduced by Brave. For those not happy, blame the Chromium project. If you look, you’ll see this is in Edge, Chrome, Comet, and other Chromium based browsers.

Enabling/Disabling Split View

As of this moment, there is no way to completely disable Split View. The dev team at Brave will be taking a look and have a discussion whether this is something they would like to dedicate time into trying to implement themselves.

Context (right click) menu

When Split View was introduced by Chromium, it was put in the location as Open in new window had been when right clicking on a link and they moved the Open in new window down lower. Again, this was inherited by Brave since it was pushed through in the Chromium code.

Everyone at Brave has been seeing the feedback from users and there is an open Github issue. At the time of me writing this, I don’t know of any ETA but they are at least looking into it. One of the developers has been assigned to it and it has a Priority 3 (P3) ranking. You can try to track that at the link below.

Final Note:

Just keep in mind that Brave has a much smaller employee base and budget compared to Microsoft, Google, and some of these other companies. There is also a lot on their plate, with more than 10,000 requests in their issue tracker in addition to all of their normal work. People are constantly asking for a lot of changes or additions. The priorities that get attention from the dev team won’t always align with what each of us individually think are important. It’s not that they aren’t listening to us or trying, but more that they just have their own little “battle plans” to try to get us the best experience as they can.

I do see another user opened a Github request to add an option to completely disable Split View as well. Unlike the link I shared earlier, this one doesn’t have any dev interaction yet. I’m not sure if they’ll do anything with it, open their own, or if this will be a “wontfix” aspect. But figured I’d at least share it as well:

3 Likes

1 Like

Thank you for letting us know.

Getting rid of the SPLIT VIEW is a high priority! This feature, and where they’ve placed the menu selection is [REDACTED DUE TO VULGARITIES]!!!
This is personally seroius enough to move me to another browser.

3 Likes

thanks for the uodate

What about the people used to the Open in Split View placement now? For example I can count in one hand the number of times I needed to specifically use Open in New Window but since its introduction, I have been using Open in Split View all the time, used to its current placement…

1 Like

For whatever reason, this topic does seem to be an issue for some. It doesn’t bother me personally, I just look where my mouse pointer is before clicking, but it has generated heated comments from a few.

From my understanding, the context menu aspect has been added to Nightly and it will “ride the train” into Stable/Release. What this means is it will come naturally when the version 1.89.41 arrives.

There is potential for them to uplift it (meaning to add it to a update sooner), but I’m not sure if it would be done or at what point. Anyway, if you’re using Nightly, you should see the change such as below:

1 Like

Just a quick follow-up. The context menu change should be coming in the next update or so. Whenever it hits 1.88 or later, basically.

I would be glad to see either an enable/disable feature or the option to move the menu to the bottom. I can see the feature being useful on ultra-wide monitor, which i dont have.

When i was programming for windows decades ago, there was a ressource-editor (inside visual studio), where you could simply remove unwanted ressources. Is something like that still available?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.