api.HTMLInputElement.webkitdirectory - can not upload on chrome while safari is ok

What type of issue is this?

Browser bug (a bug with a feature that may impact site compatibility)

What information was incorrect, unhelpful, or incomplete?

MacBookPro14,1 macOS Monterey 12.6.6
Chrome version 114.0.5735.198（stable） (x86_64)

on this page: https://developer.mozilla.org/en-US/docs/Web/API/HTMLInputElement/webkitdirectory
I can upload file on Safari by click the demo button, but the same time, I click the same button on Chrome, nothing happened.

but it's all ok on another Chrome version 114.0.5735.198（stable） (x86_64) with Mac Studio Apple M2 Max, macOS Ventura 13.4

What browsers does this problem apply to, if applicable?

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

What did you expect to see?

can upload file on Chrome version 114.0.5735.198（stable） (x86_64) with MacBookPro14,1 macOS Monterey 12.6.6

Did you test this? If so, how?

MacBookPro14,1 macOS Monterey 12.6.6
Chrome version 114.0.5735.198（stable） (x86_64)

on this page: https://developer.mozilla.org/en-US/docs/Web/API/HTMLInputElement/webkitdirectory

1. I can upload file on Safari by click the demo button, but the same time, I click the same button on Chrome, nothing happened.

2. but it's all ok on another Chrome version 114.0.5735.198（stable） (x86_64) with Mac Studio Apple M2 Max, macOS Ventura 13.4

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/HTMLInputElement/webkitdirectory

MDN metadata

MDN page report details

• Query: api.HTMLInputElement.webkitdirectory
• Report started: 2023-07-08T10:09:43.862Z

Start with the MDN page for HTMLInputElement.webkitdirectory and the browser-compat-data entry identified by the api.HTMLInputElement.webkitdirectory query. Reproduce the reported Chrome and Safari behavior on the stated macOS setups, then determine whether the compatibility data needs an evidence-backed correction or whether this is an environment-specific browser bug.