1667098 - [macOS 11 ] Close tab 'x' or new tab '+' button do not highlight on hover on macOS 11

Status: RESOLVED DUPLICATE of bug 1663467

(Core :: Widget: Cocoa, defect)

Description

[Clara Guerrero ( Need Info Brindusa Tot Please)]

+++ This bug was initially created as a clone of Bug #1663467 +++

Steps to reproduce:
1- Have some tabs open.
2- Hover over 'X' or '+' buttons

Expected Results:
Buttons should highlight when hovering over.

Actual Results:
Buttons won't highlight on hover, unless you hover the mouse over the very lowest part of the tab or you access full screen mode.

Affected versions:
Aurora 82.0b2
Nightly 83.0a1 (2020-09-23) (64-bit)

Affected platforms:
MacOs11.0
(iMac (Retina 4k, 21.5-inch, 2017)
GPU Radeon Pro 500 series

Note:
Suggesting S2 severity as it makes it hard to choose tab or close/open tab sometimes.

Comment 1

[Haik Aftandilian [:haik]]

@Clara, could you include the version of macOS 11 Beta you are hitting this problem with? We need to know which Beta you are running and they are identified by a short code such as 20A5374i. See attached screenshot of the "About this Mac" screen.

This sounds like a dupe of bug 1663467 which we believe was addressed by a fix in macOS 11 Beta 7. Did you mean to create a clone of that bug because the problem is still occurring for you?

Comment 2

[Haik Aftandilian [:haik]]

Attachment: "About This Mac" example with macOS 11 Beta build name highlighed.

Comment 4

[Haik Aftandilian [:haik]]

Thanks. The version you have is macOS 11 Beta 6 which is known to have this problem. Newer versions of the Beta are available, but I don't know if they are available via the public beta or only for users with Apple developer accounts.

Either way, I think we should close this bug as a duplicate of bug 1663467 given that you are on the build we know has the problem.

If you would like to leave it open, please retest when you are able to get an updated macOS 11 Beta.

Comment 5

[Cristian Fogel [:cfogel]]

@Haik, according to the information on the wikipedia page:

11.0 developer beta 6 20A5364e September 3, 2020
11.0 public beta 3
11.0 developer beta 7 20A5374g September 17, 2020
11.0 developer beta 8 20A5374i September 22, 2020
11.0 public beta 4

As we don't have developer accounts we test with public beta releases.
DeveloperBeta6 coincides with PublicBeta3 (20A5364e), what we tested on was 20A5374i (DeveloperBeta8/PublicBeta4).
So the issue should have been fixed on the device Clara was testing as well. That was the main reason for this bug, since for the rest of the devices involved in our testing the issue no longer manifests.

Comment 6

[Julien Cristau [:jcristau]]

Cristian, the screenshot attached in comment 3 shows 20A5364e, not 20A5374i.

Comment 7

[Cristian Fogel [:cfogel]]

Yep, was looking at the wrong comment. Thanks for the confirmation!

Comment 9

[Andrew Moff]

This bug has resturned in Big Sur Beta 9