Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chrome: Unable to upload HEIC image through post editor #66291

Open
2 tasks done
ironprogrammer opened this issue Oct 21, 2024 · 0 comments · May be fixed by #66292
Open
2 tasks done

Chrome: Unable to upload HEIC image through post editor #66291

ironprogrammer opened this issue Oct 21, 2024 · 0 comments · May be fixed by #66292
Labels
[Type] Bug An existing feature does not function as intended

Comments

@ironprogrammer
Copy link
Contributor

Description

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 WordPress/twentytwentyfive#583, then https://core.trac.wordpress.org/ticket/62268 for tracking with the 6.7 release. This issue is being reported upstream to GB.

Expected behavior

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.

Step-by-step reproduction instructions

  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.

Screenshots, screen recording, code snippet

HEIC images are not selectable in upload dialog in Chrome

Environment info

  • Hardware: MacBook Pro Apple M1 Pro
  • OS: macOS 14.6.1
  • Browser: Google Chrome 130.0.6723.59 (also confirmed working as expected on Safari 17.6, Mozilla Firefox 131.0.3)
  • Tested in local install and Playground
  • WordPress 6.7 trunk / GB not installed

Please confirm that you have searched existing issues in the repo.

  • Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

  • Yes
@ironprogrammer ironprogrammer added the [Type] Bug An existing feature does not function as intended label Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Bug An existing feature does not function as intended
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant