did you find the solution, meanwhile? sorry, i never had such issue with css menus … i would open a new document and settle up a new menu to see, if the problem persist.
dieter
yes, i’ve seen that. did you try the ccs-menu in a new document? you have even more text-issues on that page (the bodytext is black in firefox …), so you may have some conflicts with text/styles …
dieter
Clean up these styles and the menu should start appearing as intended in Firefox again. On another note I would strongly suggest you replace the current menu with one created using the CSS Menus Action that ships with Freeway. At the moment each menu item and divider is a separate layer on your page which makes the page code overly complex and slow to load. Redoing this as a CSS Menu should be easy enough and will create a lot less code on the page, which in turn means the page should load a bit faster too.
Regards,
Tim.
On 13 Mar 2013, at 13:55, Trey Yancy wrote:
I don’t know why Firefox would ignore the settings. The font is Verdana. Nothing Special.
Hi Trey,
Apologies but I was incorrect in my last email. There are errors in that CSS but they aren’t in the font-face styles (which are coming from Google). The errors are in your font sets and in how I suspect you’ve copied the font names from Google’s web site.
If you open the Edit > Font Sets dialog and select the ‘Oxygen’ set you should see the following two fonts listed;
'Oxygen', sans-serif;'
change this to read;
'Oxygen', sans-serif
Do the same with the font set ‘Gruppo’ by removing the extra semi-colon on the end;
'Gruppo', cursive;
to become;
'Gruppo', cursive
Be careful when you add any text into the font sets dialog as Freeway won’t police it for you and will simply output what you enter. A stray semi-colon or quote mark will cause some browsers to fall over and ignore the style.
Regards,
Tim.
On 13 Mar 2013, at 20:00, Trey Yancy wrote:
How do I clean this up? It was all generated by the CSS Menus Action.