I agree, don't understand why you would want to use a fieldset for navigation. always use the UL,OL,DL depending on navigation type.
It also doesn't have to be housed with-in a div, unless it is required for some other reason than positioning. As a UL is a block level element and position in the same manner as a div! Hope this helps >I would generally avoid a fieldset for navigation item's. If you can >accomplish the effect you want with div's then use your div's. The main time >a fieldset is used is to hold form element's. > >This is from the W3C site http://www.w3.org/TR/WCAG10-HTML-TECHS/ > >The following HTML 4.01 mechanisms group content and make it easier to >understand.: > > * Use FIELDSET to group form controls into semantic units and describe >the group with the LEGEND element. > * Use OPTGROUP to organize long lists of menu options into smaller >groups.. > * Use tables for tabular data and describe the table with CAPTION. > * Group table rows and columns with THEAD, TBODY, TFOOT, and COLGROUP. > * Nest lists with UL, OL, and DL. > * Use section headings (H1 - H6) to create structured documents and >break up long stretches of text. Refer to the following section for more >information. > * Break up lines of text into paragraphs (with the P element). > * Group related links. Refer to the section Grouping and bypassing links > >All of these grouping mechanisms should be used when appropriate and >natural, i.e., when the information lends itself to logical groups. Content >developers should not create groups randomly, as this will confuse all >users. > >Your list is using the <ul> and <li> selector's which the fieldset element >is not designed to work with > > >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On >Behalf Of Adam Cooper >Sent: 30 July 2008 02:35 >To: [email protected] >Subject: [WSG] Firefox 3 and fieldset elements > >Hi all, > >Just wondering if anyone can shed some light on this - >I have a relatively positioned element with a nav element inside this. > >* The relatively positioned element has a 4em top margin and 40px top >padding. > >* The nav element is positioned absolutely (top 0; right 25px) with a >negative top margin the same as it's height (3em). > >If the relatively positioned element is a div, this displays fine in >Safari 3, FF3 and Opera 9.5. >However, if I change this element to a fieldset, it breaks under FF3. > >http://www.perkler.com/ff3_problem/div.html >http://www.perkler.com/ff3_problem/fieldset.html > >To make matters worse, Firebug reports no difference in the computed >styles between the div and fieldset elements. >In fact, when using Firebug to highlight the navigation element, it >shows a "ghost" element where the navigation should be. > >The problem is the same whether the page is served as text/html or >application/xml+xhtml. > >Cheers, >Adam > > > > >******************************************************************* >List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm >Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm >Help: [EMAIL PROTECTED] >******************************************************************* > > > >-- >No virus found in this incoming message. >Checked by AVG. >Version: 7.5.524 / Virus Database: 270.5.6/1577 - Release Date: 28/07/2008 >06:55 > > > > >******************************************************************* >List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm >Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm >Help: [EMAIL PROTECTED] >******************************************************************* > -- Barry Wardrop redRoute Creative t: +44 01502506832 w: www.redroutecreative.co.uk e: [EMAIL PROTECTED] ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
