api.HTMLElement.popover - popover hint demo crashes latest chrome with STATUS_BREAKPOINT

[daverusso]

What type of issue is this?

Incorrect support data (example: BrowserX says "86" but support was added in "40")

What information was incorrect, unhelpful, or incomplete?

1. opened https://mdn.github.io/dom-examples/popover-api/popover-hint/ on Windows 10 chrome Version 138.0.7204.97 (Official Build) (64-bit)
2. clicked on one popover button
3. hovered mouse over all buttons and the page crashed with an "Aw, Snap! ... Error code: STATUS_BREAKPOINT"

What browsers does this problem apply to, if applicable?

Chromium (Chrome, Edge 79+, Opera, Samsung Internet)

What did you expect to see?

the tooltips

Did you test this? If so, how?

see description above

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

No response

Do you have anything more you want to share?

No response

MDN URL

https://developer.mozilla.org/en-US/docs/Web/API/Popover_API

MDN metadata

MDN page report details

• Query: api.HTMLElement.popover
• Report started: 2025-07-06T15:55:35.366Z

[chrisdavidmills]

Hi @daverusso, and thanks for filing this. This didn't happen when I first documented it, so it sounds like a regression.

I am on macOS, and I've done some testing of my own. I can reproduce the error you describe on the latest Chrome release version (which has nearly the same major and minor version numbers as yours). It looks like the error occurs when you open a menu and then try to mouse over the same menu button you just opened to reveal the tooltip — at this point, the tooltip doesn't show, and then you get the crash.

However, when I tested it Chrome Canary, I didn't get the crash, so it looks like this one has probably been fixed in a later version.

Can you try testing it on Chrome Canary on Windows, to see if you still get the crash? If not, I reckon we can probably close this. If so, then it is probably worth filing a bug over on the Chromium issues site: https://issues.chromium.org/home.

[daverusso]

it is probably worth filing a bug over on the Chromium issues site

I think I already did. It was a Google bug tracker. I'll check to make sure. Sadly, Canary seems to behave the same on my Windows 10 desktop. Thanks for the rapid response! dave

…

On Mon, Jul 7, 2025 at 1:22 AM Chris Mills ***@***.***> wrote: *chrisdavidmills* left a comment (mdn/browser-compat-data#27243) <#27243 (comment)> Hi @daverusso <https://github.com/daverusso>, and thanks for filing this. This didn't happen when I first documented it, so it sounds like a regression. I am on macOS, and I've done some testing of my own. I can reproduce the error you describe on the latest Chrome release version (which has nearly the same major and minor version numbers as yours). It looks like the error occurs when you open a menu and then try to mouse over the same menu button you just opened to reveal the tooltip — at this point, the tooltip doesn't show, and then you get the crash. However, when I tested it Chrome Canary, I didn't get the crash, so it looks like this one has probably been fixed in a later version. Can you try testing it on Chrome Canary on Windows, to see if you still get the crash? If not, I reckon we can probably close this. If so, then it is probably worth filing a bug over on the Chromium issues site: https://issues.chromium.org/home. — Reply to this email directly, view it on GitHub <#27243 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACNTDAXGTEWPKECCQ7VWQU33HIU5TAVCNFSM6AAAAACA4MJQP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTANBTHE2DQMZXGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[daverusso]

Doh! I rebooted and now Canary Windows 10 seems to be working! :) I'll track down my google bug report to update it. Sorry about the spam, please feel free to close the issue. Thanks again for your help. dave On Mon, Jul 7, 2025 at 6:19 AM dave russo ***@***.***> wrote:

…

it is probably worth filing a bug over on the Chromium issues site I think I already did. It was a Google bug tracker. I'll check to make sure. Sadly, Canary seems to behave the same on my Windows 10 desktop. Thanks for the rapid response! dave On Mon, Jul 7, 2025 at 1:22 AM Chris Mills ***@***.***> wrote: > *chrisdavidmills* left a comment (mdn/browser-compat-data#27243) > <#27243 (comment)> > > Hi @daverusso <https://github.com/daverusso>, and thanks for filing > this. This didn't happen when I first documented it, so it sounds like a > regression. > > I am on macOS, and I've done some testing of my own. I can reproduce the > error you describe on the latest Chrome release version (which has nearly > the same major and minor version numbers as yours). It looks like the error > occurs when you open a menu and then try to mouse over the same menu button > you just opened to reveal the tooltip — at this point, the tooltip doesn't > show, and then you get the crash. > > However, when I tested it Chrome Canary, I didn't get the crash, so it > looks like this one has probably been fixed in a later version. > > Can you try testing it on Chrome Canary on Windows, to see if you still > get the crash? If not, I reckon we can probably close this. If so, then it > is probably worth filing a bug over on the Chromium issues site: > https://issues.chromium.org/home. > > — > Reply to this email directly, view it on GitHub > <#27243 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ACNTDAXGTEWPKECCQ7VWQU33HIU5TAVCNFSM6AAAAACA4MJQP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTANBTHE2DQMZXGM> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

[chrisdavidmills]

No worries, @daverusso, glad you took the time to explore it.