Directory

[Safari browser] Local font upload not working as expected · Issue #302 · WordPress/create-block-theme · GitHub
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

[Safari browser] Local font upload not working as expected #302

Closed
matiasbenedetto opened this issue Apr 4, 2023 · 6 comments
Closed

[Safari browser] Local font upload not working as expected #302

matiasbenedetto opened this issue Apr 4, 2023 · 6 comments

Comments

@matiasbenedetto
Copy link
Contributor

Local font upload not working as expected on Safari browser:

In the video, we can see that the font metadata is not being read and completed in the form. If the form is completed manually the submit button is still disabled. Chrome, Firefox, and Gnome Browser are working as expected.

Thanks, @beafialho for reporting this and recording the screencast.

cbt_bug.mp4
@vcanales
Copy link
Member

vcanales commented Apr 4, 2023

I could not reproduce this issue on Safari Version 16.3 (18614.4.6.1.6), on an M1 MacBook Pro. Uploading the same font used by @beafialho in the video didn't help; the font is previewed, and the form is auto-filled correctly.

image

@jeffikus
Copy link
Contributor

jeffikus commented Apr 4, 2023

I tested this with Version 16.3 (18614.4.6.1.5) on m1 Macbook Pro without issue. I tested with multiple .ttf fonts including the Commissioner-LightItalic.otf font in the video.

@beafialho what hardware are you running this on?

@beafialho
Copy link

@beafialho what hardware are you running this on?

An M1 iMac and the Safari Version is 16.2 (18614.3.7.1.5).

@mikachan
Copy link
Member

mikachan commented Apr 5, 2023

Just to add another version to the mix - I also couldn't reproduce this, and I was using Safari Version 16.1 (18614.2.9.1.12). So perhaps this is a bug specific to 16.2?

@t-hamano
Copy link
Contributor

Since this feature has been integrated into the native font library, can this issue be closed?

@pbking
Copy link
Contributor

pbking commented Apr 30, 2024

Yup. Closing.

@pbking pbking closed this as completed Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants