Docs: Use proper <button> instead of faked <a> element for popover example#31399
Docs: Use proper <button> instead of faked <a> element for popover example#31399patrickhlauke wants to merge 3 commits intomainfrom
Conversation
60a201e to
7f738b5
Compare
|
only browser that currently seems to have a problem with this, from testing, is Safari. investigating further what its beef is... might set this to draft in meantime...wasn't expecting it to take that long, but seems the shortcoming/quirk there is not as straightforward as initially suspected. |
|
ok, root of the problem seems to be the fact that Safari doesn't actually focus elements like and Firefox/Mac copied that silly behavior too. good good. considering adding some basic additional behavior that also sets |
|
will likely keep this PR parked, do a separate PR for a potential cross-browser fix (or, well, a patch for Safari and Firefox on Mac), and hopefully this can then get merged when that fix is merged |
|
@patrickhlauke do we close this? |
|
yeah as i get the feeling Apple are in no rush to change their behaviour in Safari (and Firefox will just copy what Safari does on macOS for "platform consistency"), and since I doubt we want to hack away at adding extra scripting that explicitly focuses the button after a click ... i think i'll just abandon this. annoying. |
sidesteps #31391 but on principle should really use
<button>here