Bug 257245 - REGRESSION(263527@main): GrammarlyGO is broken
Summary: REGRESSION(263527@main): GrammarlyGO is broken
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on: 255454
Blocks:
  Show dependency treegraph
 
Reported: 2023-05-23 17:46 PDT by Ryosuke Niwa
Modified: 2023-06-05 08:46 PDT (History)
2 users (show)

See Also:


Attachments
Working screenshot (142.98 KB, image/png)
2023-05-23 18:00 PDT, Ryosuke Niwa
no flags Details
Broken screenshot (146.63 KB, image/png)
2023-05-23 18:01 PDT, Ryosuke Niwa
no flags Details
Reduction (301 bytes, text/html)
2023-05-23 18:44 PDT, Ryosuke Niwa
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ryosuke Niwa 2023-05-23 17:46:35 PDT
Reproduction steps:
1. Visit grammarly.com (create an account & login)
2. Click on "GrammerlyGo" on the right side pane.
3. Click on "more" in the popup that opens after (2)

Expected result:
"More" button goes away and more items will be shown.

Actual result:
"More button" stays with transparent background, overlapping with more content.
Comment 1 Ryosuke Niwa 2023-05-23 17:53:58 PDT
I'm not sure why this issue doesn't reproduce on other browsers.
Comment 2 Ryosuke Niwa 2023-05-23 18:00:36 PDT
Created attachment 466470 [details]
Working screenshot
Comment 3 Ryosuke Niwa 2023-05-23 18:01:41 PDT
Created attachment 466471 [details]
Broken screenshot
Comment 4 Ryosuke Niwa 2023-05-23 18:15:50 PDT
Hm... interesting. The issue is precisely that the button with tabindex is now getting focus and :focus style makes it visible. In Chrome, document.body is getting the focus in this case so there is some behavioral difference between WebKit and Blink here.
Comment 5 Ryosuke Niwa 2023-05-23 18:44:21 PDT
Created attachment 466472 [details]
Reduction
Comment 6 Ryosuke Niwa 2023-05-24 18:35:53 PDT
The bug reproduces on Firefox as well.
Comment 7 Radar WebKit Bug Importer 2023-05-30 17:47:17 PDT
<rdar://problem/110036456>
Comment 8 Ryosuke Niwa 2023-06-05 08:46:52 PDT
This issue seems to be fixed on grammarly.com side now.