Hi LG,
I am making a site (html5) which has a nav section at the top of each
page. Some pages will also have a 'menu' which will be a short list of links
to other pages in the site, and these will appear lower down in the content
of the page.
Instinct tells me that it is sensible to make
On 1/9/11 7:44 AM, designer wrote:
Hi LG,
I am making a site (html5) which has a nav section at the top of
each page. Some pages will also have a 'menu' which will be a short
list of links to other pages in the site, and these will appear lower
down in the content of the page.
Instinct
This is a 'too early' post as HTML5 nav nor menu aren't really supported
yet in any major browsers.
So, we are speculating about how browsers might interpret these elements.
You can read the HTML5 spec and see what is says about those tags, but at
the end of the day browser implementation is
On 09/01/2011 13:32, Jason Grant wrote:
This is a 'too early' post as HTML5 nav nor menu aren't really
supported yet in any major browsers.
So, we are speculating about how browsers might interpret these elements.
You can read the HTML5 spec and see what is says about those tags, but
at the
The nav element is the correct element to use in the case of site navigation
links. You are correct about menu which when implemented will be like a desktop
app menu.
The nav element is not generally accessibility supported in browsers yet,
which means it's semantics are not conveyed, but
Hi,
I have the following navigational menu bar. The menu has multiple
parent menu items. For the sake of the example, I only provide the first menu
item. It has about five child menu items. This is a horizontal menu bar at the
top of the ASP.Net website. What currently happens is when
On Sun, Jan 9, 2011 at 2:09 PM, Goku San gokus...@hotmail.com wrote:
I have the following navigational menu bar. The menu has multiple parent
menu items.
[snip]
What currently happens is when a user hovers over
the Parent menu item, the child menu items appear below, horizontally, of
On Jan 9, 2011, at 7:04 AM, Benjamin Hawkes-Lewis wrote:
Make the parents the containing blocks for the absolute positioning of
the children:
#nav .sub {
position: relative
}
http://reference.sitepoint.com/css/containingblock
I hope you'll ensure that users who are not using a
These two essentially are the same. I am assuming the menu is
controlled by a javascript, best practise is to use the absolute
positioning to control submenu and use the toogle or mouseover to
trigger the sub-level.
I'm not sure this is considered best practice as keyboard users would have
On Jan 9, 2011, at 10:24 AM, Thierry Koblentz wrote:
These two essentially are the same. I am assuming the menu is
controlled by a javascript, best practise is to use the absolute
positioning to control submenu and use the toogle or mouseover to
trigger the sub-level.
I'm not sure this
Hi,
Thanks for your responses! I added the, #nav .sub {position:
relative;}, removed the {display:none;} from my CSS file and from the ASPX
page. Still not getting a solution. The #nav .sub {position: relative;} helped
because it positioned the child elements directly below the
On Jan 9, 2011, at 11:42 AM, Goku San wrote:
Hi,
Thanks for your responses! I added the, #nav .sub {position:
relative;}, removed the {display:none;} from my CSS file and from the ASPX
page. Still not getting a solution. The #nav .sub {position: relative;}
helped because it
On 1/9/11 10:24 AM, Thierry Koblentz wrote:
These two essentially are the same. I am assuming the menu is
controlled by a javascript, best practise is to use the absolute
positioning to control submenu and use the toogle or mouseover to
trigger the sub-level.
I'm not sure this is considered
Hi,
I'll be out of the office from the 22nd of December 2010 until the
12th of January 2011.
For urgent inquiries, please be in touch with Georgie at
geor...@10collective.com.au
Merry Christmas
Julien
***
List Guidelines:
14 matches
Mail list logo
