I have produced a visual test page with a CSS3 menu, and have applied a CSS style involving an @fontface font to the parent container of the menu box.
On every machine without the correct font already loaded, it defaults to Impact, if present, and then slips along the created font set if that font is not present etc.
From the iPad to Mac Safari to Windows 8 IE, I can’t get the menu to display the correct font - Bebas Neue Regular, from Fontsquirrel and downloaded as a full fontface kit.
I’ve tried applying the CSS style to the actual CSS3 Menus box, directly to the highlighted menu text but all to no avail.
Is there a conflict between Caxton and CSS3 menus? I would’t have thought so… all very curious.
Freeway 5.6.5, Caxton 1.0b8, Mac OS 10.8.2
http://www.fear-of-bicycles.co.uk/rumble/
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
On 9 Nov 2012, at 09:10, Ian Halstead wrote:
Is there a conflict between Caxton and CSS3 menus? I would’t have thought so… all very curious.
I’m using the standard CSS menus action with Caxton on a project right now. It seems to be working as expected, though I haven’t uploaded to a server yet.
Now, did you mean CSS Menus, or is there another CSS3 Menus action I haven’t noticed yet?
I have noted on the FontSquirrel web site that some of the @fontface attributes don’t work properly on various platforms, including iOS. As far as Internet Explorer is concerned, I basically ignore it, as you would a fractious child making unreasonable demands.
Cheers
Heather
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Ah yes… I did mean CSS Menus, thanks Heather. At the moment no browser on any platform seems to work at this end.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
On 9 Nov 2012, at 10:16, Ian Halstead wrote:
At the moment no browser on any platform seems to work at this end.
Odd.
Just to check I applied the font style to the container as you did (silly me, I forgot that one when working on the design!). It still seems to function as it should.
Have you definitely got the Caxton setting, the font family settings and so on set properly?
Heather
Imagic Design * Good Design - No Compromise
email@hidden
http://www.imagic-design.co.uk
Twitter @Imagic-Design
T: 01634 864017
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Excuse me if I have this all wrong – I don’t use the Caxton action or the
CSS Menu action as I am used to rolling my own code for these things.
Your FWP code has the font-family as ‘Bebas Neue’ while it should be
‘BebasNeueRegular’ – this is how it currently reads
font-family: 'Bebas Neue', Impact, Verdana, Trebuchet, sans-serif;
That’s why it is defaulting to Impact because Bebas Neue is not the webfont
name. My best guess is that you made a font set for Freeway Pro and ‘Bebas
Neue’ is the Mac font name. If you did make a FWP font set, go back to Edit
Font Sets and open it, then change the alternative fonts to include the
webfont name like so,
'BebasNeueRegular', Impact, Verdana, Trebuchet, sans-serif
Then you will then be good to go.
–
Ernie Simpson
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Sussed it thanks to Ernie. Not the first time you’ve sorted a problem either Ernie - very much appreciated.
The font name that automatically gets generated when you select the font from the drop-down list when creating the set… I’d forgotten to replace this name with the one copied from the font CSS style sheet.
All now working perfectly. Excellent responses guys and thanks.
Ian
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options