Bug 220580 - REGRESSION (r257839): Element cannot be "focus()"ed right after becoming visible from hidden
Summary: REGRESSION (r257839): Element cannot be "focus()"ed right after becoming visi...
Status: CLOSED DUPLICATE of bug 217240
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: WebKit Nightly Build
Hardware: All All
: P2 Normal
Assignee: Nobody
Depends on:
Reported: 2021-01-12 23:04 PST by Tomoki Imai
Modified: 2021-01-14 01:38 PST (History)
3 users (show)

See Also:

Testcase (1.25 KB, text/html)
2021-01-12 23:04 PST, Tomoki Imai
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tomoki Imai 2021-01-12 23:04:38 PST
Created attachment 417510 [details]

We found a regression from r257839.

Here is how to reproduce:
1. Open the attached html with MiniBrowser
2. Push Enter key

Expected result:
Newly appeared "Menu Item" button should have focus.

Actual result:
Newly appeared "Menu Item" button doesn't have focus.

Reproduced environment:
- WinCairo MiniBrowser (r271389)

- I confirmed that reverting r257839 solves the issue.
- Chrome (87.0.4280.141) and Firefox (84.0.1) on Windows don't have this issue
- I didn't test Safari, but because the changed code in r257839 is platform-independent code, I hope it can be reproduced in Safari too.

Attached test case description:
"Menu Item" button is at first invisible, because the div which contains the button is "display:none".
When Enter key is hit, "open" class is added, and it should overwrite "display" with "block".
Then we call "focus" on the button. Because button is visible now, it should have focus.

// open menu
// focus on menu item

<div class="menu">
            <button class="menu-item">Menu Item</button>

.menu {
    display: none;
    background: #000;
.open {
    display: block;
Comment 1 Antti Koivisto 2021-01-13 05:30:44 PST
I can't repro on Safari (the menu opens fine) but I believe this is the same bug as 217240.

*** This bug has been marked as a duplicate of bug 217240 ***
Comment 2 Tomoki Imai 2021-01-13 06:02:40 PST

Thanks for the info, sorry, I'm not sure why I missed that ticket.

This bug and bug bug 217240 seems to be same.
I confirmed that attachment 417524 [details] in bug 217240 fixes this issue.
Comment 3 Antti Koivisto 2021-01-14 01:38:51 PST
Thanks for confirmation!