Open frypf opened 2 years ago
@frypf We need more information here. How did you configure the group policy? Did you apply the same group policy on Chrome? It's the same UI just different styling so I'm surprised you wouldn't have this issue in Chrome as well.
I applied the group policy (URLAllowList
) via defaults write
in Terminal on MacOS, and yes I applied the same to both Brave and Chrome. With regard to Chrome having different styling rather than UI, yes this is what I meant - just a case of imprecise language on my part. Indeed, it seems Brave's styling changes are the actual culprit for this issue as the "More Actions" menu seems to be overlaid by the "Browser is Managed…" banner, which is not the way it's laid out in Chrome.
Chrome behaviour:
Brave behaviour:
And finally again in Brave, but with a different CSS width
specified on the <managed-footnote>
element via DevTools, the button is clickable again:
Any update on this? I see it's been labeled as P5 but the problem still exists over a year after first reporting. What additional info is required?
Description
I added group policies to allow some protocol handlers and now, as in the title, the banner stating "Your browser is managed by your organisation" stops me being able to click the "More actions"/3 dots menu on the downloads page (ie.blocking any access to "Clear all" & "Open downloads folder").
Steps to Reproduce
Actual result:
Menu is un-clickable (although keyboard access is still possible via multiple presses of Tab and then Spacebar).
Expected result:
Clicking the menu should open the menu.
Reproduces how often:
Every time.
Brave version (brave://version info)
1.39.111 Chromium: 102.0.5005.61 (Official Build) (x86_64) but has been present for some time - I've only just put 2+2 together as to what the specific cause was.
Other Additional Information:
Doesn't happen on Chrome because their UI is different on the downloads page.
Miscellaneous Information:
I opened DevTools and tried either hiding the banner completely or even just changing its width via CSS. Both of which resolved the problem, but obviously this is pretty inconvenient to repeat every time.