Closed (works as designed)
Project:
@font-your-face
Version:
7.x-2.6
Component:
Code (general)
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
4 Dec 2012 at 18:16 UTC
Updated:
11 Dec 2012 at 17:22 UTC
I was only able to duplicate this error with one font. Set to Code (general) because not sure if this is an issue in general or just for the specific font from the Font Squirrel provider.
Feel free to edit this title. I think the line below is AJAX but I don't program...
Steps to duplicate:
The page only loads the following: [{"command":"settings","settings":{"basePath":"\/","pathPrefix":"","ajaxPageState":{"theme":"library_love","theme_token":"dMqcZbyn37sp14Ssy2dhRxUmUgk6fjU9vVL2QELGrco"}},"merge":true}]
I looked for duplicate posts and didn't see any. My apologies if someone has already reported it.
Comments
Comment #1
Courtney.B commentedI forgot to include some more information.
The whole Puritan family causes the above problem. Other fonts from Font Squirrel that I've tested work as expected when clicking on the Cancel button.
Comment #2
Courtney.B commentedSame thing happened again with an Edge font today. I had clicked the "submit" button and received a similar message to what I reported above.
Comment #3
Drave Robber commentedI could not reproduce this, but, as #1859240: Edge fonts show as generic serif in preview suggests, this is not the only AJAX-related problem for you, so disabling AJAX might be an option. (Unless you have a client who is a huge fan of AJAX throbbers and wants to see them everywhere, that is :)
I notice however Puritan 2.0 is broken on the FontSquirrel's end and cannot work as it is. The API return for the family states
fontface_nameas e.g."fontface_name":"Puritan2.0Normal", while supplied CSS has it like:If you're desperately interested in that font and if it's really different from Puritan available from Google or Edge Fonts, this is an issue to raise with FontSquirrel.
Comment #4
Courtney.B commentedI'm not using the Puritan font family - was just randomly clicking on fonts to see what happened. >.>
I'm going to close this issue because it looks like it's an issue with my particular set-up in regards to AJAX. If someone else can duplicate this issue, feel free to re-open.
Thanks again for the fast reply!