Chrome: Unable to upload HEIC image through post editor

[ironprogrammer]

Using Chrome's built-in upload functionality when inserting an HEIC image with the post editor, files of type HEIC are disabled for selection. However, files can be added through drag-n-drop on the Image block, or added through the media library either with the upload or multi-file feature. This issue occurs regardless of server-side HEIC support (i.e. availability of ImageMagick.)

Originally reported at ​https://github.com/WordPress/twentytwentyfive/issues/583.

Testing Instructions

Steps to Reproduce

1. In Chrome, add a new post.
2. Add an Image block, and select "Upload".
3. 🐞 Observe that HEIC images cannot be selected for upload.

Expected Results

When testing a patch to validate it works as expected:

• ✅ Though Chrome cannot display HEIC natively, it should be an allowed filetype in the browser uploader. This is consistent with ​6.7 support for this media type.

When reproducing the bug:

• ❌ HEIC files are not selectable for upload.

Supplemental Artifacts

[adamsilverstein]

Hi @ironprogrammer - thanks for opening this. The fix may require an upstream ticket in Gutenberg.

[adamsilverstein]

I was able to reproduce this bug in Chrome. Selecting .heic images works as expected in Firefox and Safari in my testing.

[adamsilverstein]

Adding "image/heic" to the accepted types for the upload button fixes the issue for me. I made the change in dev tools then was able to select heics.

This will need to change in Gutenberg.

[swissspidy]

@adamsilverstein I think this warrants a bug in Chromium, actually.

I just found ​https://g-issues.chromium.org/issues/355003187, which is for videos, but it shows how the hardcoded image list hasn't been updated to include `image/heic1: ​https://source.chromium.org/chromium/chromium/src/+/main:net/base/mime_util.cc;l=669-692;drc=2017cd8a8925f180257662f78eaf9eb93e8e394d

Edit: see also ​https://g-issues.chromium.org/issues/40860796

[ironprogrammer]

Thank you, @adamsilverstein and @swissspidy 🙌🏻

I've reported this upstream on ​https://github.com/WordPress/gutenberg/issues/66291. Does a 6.7 fix (or workaround) seem feasible here?

[adamsilverstein]

Here is a proposed fix for GB ​https://github.com/WordPress/gutenberg/pull/66292

@adamsilverstein I think this warrants a bug in Chromium, actually.

yeah, it does feel like a bug. Maybe still worth fixing unless it gets fixed in Chrome quickly. I could add a comment in the PR.

[pbiron]

I can confirm that FF works on Windows but that Chrome & Edge don't. Chrome and Edge both being based on Chromium suggests that @swissspidy is correct that the bug is in Chromium.

And also agree that a short term workaround in GB is a good idea until the Chromium bug is fixed.

[swissspidy]

Opened a new Chromium issue just in case with a suggested fix: ​https://g-issues.chromium.org/issues/375118901

[ironprogrammer]

Because this has been reported in GB (comment:5) and added to the ​6.7 editor board, as well as reported with Chromium (comment:8, thanks, @swissspidy!), I'm marking this with reported-upstream.

[mayanktripathi32]

The upstream issue:​https://issues.chromium.org/issues/375118901 has been marked as resolved and is now supported in Chrome Canary. I successfully tested adding HEIC and HEIF images using the images/* MIME type.

Tested Version: 133.0.6846.0 (Official Build) Canary (arm64).