Bug 257245

Summary: REGRESSION(263527@main): GrammarlyGO is broken
Product: WebKit Reporter: Ryosuke Niwa <rniwa>
Component: DOMAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: rbuis, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on: 255454    
Bug Blocks:    
Attachments:
Description Flags
Working screenshot
none
Broken screenshot
none
Reduction none

Ryosuke Niwa
Reported 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.
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
View All Add attachment proposed patch, testcase, etc.
Ryosuke Niwa
Comment 1 2023-05-23 17:53:58 PDT
I'm not sure why this issue doesn't reproduce on other browsers.
Ryosuke Niwa
Comment 2 2023-05-23 18:00:36 PDT
Created attachment 466470 [details] Working screenshot
Ryosuke Niwa
Comment 3 2023-05-23 18:01:41 PDT
Created attachment 466471 [details] Broken screenshot
Ryosuke Niwa
Comment 4 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.
Ryosuke Niwa
Comment 5 2023-05-23 18:44:21 PDT
Created attachment 466472 [details] Reduction
Ryosuke Niwa
Comment 6 2023-05-24 18:35:53 PDT
The bug reproduces on Firefox as well.
Radar WebKit Bug Importer
Comment 7 2023-05-30 17:47:17 PDT
<rdar://problem/110036456>
Ryosuke Niwa
Comment 8 2023-06-05 08:46:52 PDT
This issue seems to be fixed on grammarly.com side now.
Note You need to log in before you can comment on or make changes to this bug.