Bug not resolved

[thecs]

Fake tab strip shows up

Description of the issue: Random, or most probably, the previous tab shows as a fake tab in the tab strip at the bottom. Sometimes, tabs opened in Incognito mode appear in the normal tab, which is really concerning. It is not clickable; as soon as I open up the whole tab view page, the fake tab strip disappears. Expected result: it should not show the fake tab Brave Version( check About Brave):1.84.133 Mobile Device details Android 11 Additional Information: It’s happening for more than 2…

@Mattches the above post is closed but the issue is still there

[leh]

Don’t know about the incognito part, but I can reproduce the fake tab strip on Brave beta 1.86.128.
If you stay on a tab inside a group for 3 seconds or more, then open the tab switcher and switch to a single tab, the fake tab group strip will appear.
You can see in my screen record.
The 1st time, I stayed in a grouped tab for more than 3s, the bug occurred.
The 2nd time (from 13s in the video), I stayed in a grouped tab for less than 3s, the bug didn’t occur.
The 3rd time (from 20s in the video), I stayed in a grouped tab for more than 3s then switched to another grouped tab, stayed on this tab for less than 3s, the bug didn’t occur.

edit: This bug only happens if I use “Enable bottom navigation toolbar” in Settings > Appearance.

[289wk]

@Mattches - OP reports “the above post is closed but the issue is still there”

And, @leh reports, above “can reproduce the fake tab strip on Brave beta 1.86.128” . . . and also reports “bug only happens if I use Enable bottom navigation toolbar in Settings > Appearance”.

[Mattches]

I can re-open the thread if you’d like. The Github issue is still open and active: https://github.com/brave/brave-browser/issues/47959

[thecs]

As I mentioned in the last closed post, the issue I reported is not related to the Git issue you shared.

In the previous post, I was unable to provide an Incognito tab recording of the fake tab strip because I did not know the steps to reproduce the bug. However, thanks to @leh comment, I was able to reproduce the issue and record it in an Incognito tab as well.

I am now sharing the video with you. Kindly please check this, as this issue has been ongoing for more than 6–7 months.

@Mattches

[Mattches]

I see, apologies on that. However I do believe we’ve captured this issue already – this one seems to match:

`tab group` toolbar being displayed when opening a new `non-group tab` from a `tab group`

tab group toolbar being displayed when opening a new non-group tab from a tab group #51883

[Mfh1973]

Does brave just stop trying to fix some bugs after awhile? Like this one and the video dimming or going black one that’s been going on for a lot longer?

[Mattches]

@Mfh1973 as you can see in the above issue, it’s been moved into the appropriate project board and is ready to be worked on.

The screen dimming issue occurs in other Chromium browsers as well so it likely needs an upstream fix. That said, there is a potential workaround in the meantime that has worked for some users you can try changing these flag values:

1. Disable Tab Strip Group Drag Drop Android flag.
2. Disable Block screen fingerprinting flag.
3. Enable Enables use of the screen parameter for requestFullscreen flag.

Make sure you relaunch after changing the flags and test to see if the issue is resolved for you. Issue is being tracked here:

Users reports - screen is dimming & locking while videos are playing in Brave

[thecs]

@Mattches I’m really getting tired of hearing “it’s an upstream issue” every time something breaks.

You guys are a big browser company, and you’re milking Chromium hard — you don’t even contribute back. Microsoft devs go in and fix things upstream, but you just sit back, patch things in your fork, and call it a day. It’s not fair to the open-source community. You’re taking the whole cake and giving nothing back. If you’re gonna use Chromium, at least help make it better.

[MasterLink]

@thecs

I’m really getting tired of hearing “it’s an upstream issue” every time something breaks.

I’m going to say this as politely as possible, but as someone who’s developed code in assembly since the days of the 8086 and 68000, let me be clear.

Upstream issues happen, and all forks get affected by it. Things take time.

@thecs

Microsoft devs go in and fix things upstream

Microsoft also has a lot more employees.

Brave has not only less money, they have less developers. They also are fixing a variety of other issues, many of which are upstream.

Guess what I do as a fellow Brave user who helps others, I have multiple browsers installed. Chromium (where all these browsers come from) for one, because many of the issues people have here, can be replicated there. Chromium is the upstream code.

I suggest you learn some patience here, because getting mad will only slow things down as they deal with people arguing with them, when they can be trying to push reports or fixes upstream. This arguing and banter about the upstream issue is counterintuitive.

@thecs

but you just sit back, patch things in your fork, and call it a day. . . . . . . .You’re taking the whole cake and giving nothing back.

They are an active contributor. Saying things without proof is slander, just an FYI.

AUTHORS

Line 1800:

That wasn’t added there just for lols. Again, be careful with slander.

Now for the meat and bones of the issue: Brave can’t just willy nilly fix things. Some browsers may already be working on their own “workaround” to certain Chromium bugs, so if that was just fixed it breaks other forks then. Also Google is still primary contributor to Chromium, around 94% in 2024 alone. Of course every other company is going to look like peas as a contributor. Also, Brave’s contribution’s usually are privacy focused. It is their specialty after all.

Hope this helps and clears up the world of software development.

[thecs]

I don’t know, man — I’m facing a lot of bugs in Brave right now. Whenever I look them up, most of them are labeled as “upstream issues.” That might make sense from a development perspective, but as an end user, I honestly don’t care whether it’s Chromium or some other engine underneath.

These issues have been around for months, sometimes even longer, with no fix in sight. I’ve reported some of them directly to Brave, but they just get marked as upstream issues. As a Brave user, if I report a problem, I expect Brave to take ownership of it and fix it — or at least provide a clear workaround or timeline — not just pass it upstream and leave users waiting for months or even a year.

[MasterLink]

@thecs

but as an end user, I honestly don’t care whether it’s Chromium or some other engine underneath.

I get it, I’m an end user too. But I also have been working with computers long enough to know how forks work. When you use a fork, this happens.

So again, you can’t force something just because as an end user you don’t like it. We don’t like it either, and I bet the devs don’t either. But again it does take time.

@thecs

These issues have been around for months, sometimes even longer, with no fix in sight.

I’m gonna link you to one of my own complaints and lead by example here: Broken 30-bit color when ACM enabled with scRGB color space

See how the issue not only went unsolved and ignored? Check my edits and my own replies to myself, I ended up realizing it was a Chromium regression. So know what I did? Filed a ticket with Chromium. But guess what, it went nowhere there as well.

Do I expect Brave to fix it? Well, no. They specialize in privacy, security, that stuff. Half the devs probably don’t even have a setup like mine to have a 30-bit color depth to use the color space I use, so it falls in the cracks.

Point is, I found where the issue was, and don’t blame nor expect Brave to fix it, because I know Brave is a fork of Chromium.

@thecs

not just pass it upstream and leave users waiting for months or even a year.

Do realize, it’s Chromium’s developers that leave users waiting months to years. I know, I’ve dealt with them in the past.