Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...DNNMenuNavigationProvider + css + mozillaDNNMenuNavigationProvider + css + mozilla
Previous
 
Next
New Post
6/27/2007 7:49 PM
 

Hello

I'm experiencing the same issue. 

It seems that the css width and height settings are not being picked up by firefox - and the menu is formatting differently for this browser.

I can't find a way to override it. 

Unfortunately, my development is hidden behind a firewall, but if you'd like any more materials or setup information I will endeavour to help.

Until then, I'll watch this thread with interest.

Regards
Ian

 
New Post
6/28/2007 9:19 AM
 

The DNNMenu does not use tables for its root items, and can be configured to not use them for submenus as well (lots of people think tables are evil...  I'm not one of them, but I try and listen and incorperate what people are asking for).  Instead it uses SPAN tags.  SPAN tags are inline elements, which get their height/widths ignored.  I believe that you can override this behavior by making them inline-blocks or using line-height...  I'd rather deal with tables than all the inconsistencies between browsers in regards to css.

I am considering making the next version of the menu allow for tables at the root as well.  If someone else has a better solution for what element would be best to use for the root elements speak up.


 
New Post
6/28/2007 7:37 PM
 

Jon

Thanks for your interest and response.

I'll be able to make some recommendations to our client - basically to lose the background tab images and use a solid colour background.  That way, difference in menu position, width and height does not make such a serious impact between browsers.

DIV may be more appropriate than SPAN, because as you say, SPAN is an inline tag and the menus are basically individual elements (better suited to DIV).   Allowing for tables at the root (I'm reading into this that you'll be allowing this as an option) is also a great idea and should go some way towards providing greater flexibility.

At the same time, I'm reluctant to just jump in and say "you should do it this way" as I haven't been an active member in this project to date, and there's no doubt a lot of background and history as to why past decisions have been made. Clearly you've put in a lot of research and effort - and to have 3rd party "experts" jump in and offer advice may not be as helpful as it may seem at first. 

In the meantime, I'll be able to go back to our client, and say I've discussed this with the developer of the menu system and they can't have custom tabs on each menu item for this release, AND have it looking exactly the same in Firefox - for this release anyway.  This will be workable for me.

Thanks again for your input.

Ian

 
New Post
7/3/2007 1:11 AM
 

Hi

I have a temporary fix which will work for now.

As per Jon's advice, line-height does work, and I have padded the text (page name) with    characters to pad it out in firefox.

It does make the breadcrumbs and site map links look a little quirky, but I've reducted that by not underlining the links in those sections.

Thanks
Ian

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...DNNMenuNavigationProvider + css + mozillaDNNMenuNavigationProvider + css + mozilla


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out