[css-d] Menu-issue
Link : ikjensen.dk/test/ Wanted: Top-nav : Moving the second sublevel to about 5px below Top-nav. So there will be a small white border at the top. There are only Sublevels in the First menuentry. Last four. Do I have to write a class or something to get the position or . PS! Walidating the template says a lot of errors. Is't because of the Menu-structure or just "bad" coding. -- Regards / Mhv. Ib K. jensen __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
[css-d] menu issue
Puzzling one here folks. Development site at http://db-studio.venus.titaninternet.co.uk/index.php Although there is no change to the html, I have had to add an extra style code in the contact and portfolio pages as the menu sits a few pixels higher than does than it does on the other pages. Please ignore the validation errors which are caused by the cms editor (something over which I have no control) - don't believe that these are influencing this issue. Best Ian Young Director IYES e-Solutions Specialists __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Menu-issue
On 28/12/08 16:58, Ib Jensen wrote: > Do I have to write a class or something to get the position or . You can use descendant selectors to target lists that are descendants of other lists: http://css.maxdesign.com.au/selectutorial/selectors_descendant.htm That's likely all you need here. > Walidating the template says a lot of errors. Is't because of the > Menu-structure or just "bad" coding. Verbose validator output: http://tinyurl.com/97gl83 Bad coding, mostly reflecting a failure to always open and close tags are required in XHTML: http://www.w3.org/TR/xhtml1/#h-4.3 (Note also: http://www.w3.org/TR/xhtml1/#C_2 if you try to fix this.) I'd recommend removing errors from your HTML layer before making any further CSS changes. -- Benjamin Hawkes-Lewis __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Menu-issue
2008/12/28 Benjamin Hawkes-Lewis : > On 28/12/08 16:58, Ib Jensen wrote: >> > You can use descendant selectors to target lists that are descendants of > other lists: > http://css.maxdesign.com.au/selectutorial/selectors_descendant.htm > That's likely all you need here. > > Verbose validator output: http://tinyurl.com/97gl83 > > Bad coding, mostly reflecting a failure to always open and close tags are > required in XHTML: > http://www.w3.org/TR/xhtml1/#h-4.3 > (Note also: http://www.w3.org/TR/xhtml1/#C_2 if you try to fix this.) > I'd recommend removing errors from your HTML layer before making any further > CSS changes. If I can't get this working, I'll find another menu-solution. Thanks for the links. -- Regards / Mhv. Ib K. jensen __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Menu-issue
2008/12/28 Benjamin Hawkes-Lewis : > On 28/12/08 16:58, Ib Jensen wrote: >> > I'd recommend removing errors from your HTML layer before making any further > CSS changes. Done ! And (x)HTML and CSS are validating perfectly now. Now I'm just going to find out how to adjust the menu. -- Regards / Mhv. Ib K. jensen __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Menu-issue
Ib Jensen wrote: > Link : ikjensen.dk/test/ > > Wanted: > > Top-nav : > Moving the second sublevel to about 5px below Top-nav. So there will > be a small white border at the top. > There are only Sublevels in the First menuentry. Last four. > > Do I have to write a class or something to get the position or . > > PS! > Walidating the template says a lot of errors. Is't because of the > Menu-structure or just "bad" coding. > > I got it to validate if it helps any :) http://dwabbott.com/iktest.html -david -- Powered by Gentoo GNU/LINUX http://www.linuxcrazy.com pgp.mit.edu __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Menu-issue
2008/12/28 David :
> Ib Jensen wrote:
> I got it to validate if it helps any :)
> http://dwabbott.com/iktest.html
> -david
Me too.
I don't know if you read my answer to Benjamin Hawkes-Lewis.
Now, only the Menu-issue is left back. ;-{
--
Regards / Mhv.
Ib K. jensen
__
css-discuss [cs...@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Menu-issue
From: "Ib Jensen"
> 2008/12/28 David :
>> Ib Jensen wrote:
>
>> I got it to validate if it helps any :)
>> http://dwabbott.com/iktest.html
>> -david
>
> Me too.
> I don't know if you read my answer to Benjamin Hawkes-Lewis.
>
> Now, only the Menu-issue is left back. ;-{
You would be better off with a nice single-level CSS menu across the top
with sidebar context menus. The menu you have is extremely unusable - even
in the browsers in which it works. For that type of menu you really should
be using a scripted one.
--
Al Sparber - PVII
http://www.projectseven.com
The Finest Dreamweaver Menus | Galleries | Widgets
http://www.projectseven.com/go/pop
The Ultimate DW Menu System
__
css-discuss [cs...@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Menu-issue
2008/12/28 Al Sparber : > From: "Ib Jensen" >> 2008/12/28 David : > You would be better off with a nice single-level CSS menu across the top > with sidebar context menus. You mean, just a single-level drop-down menu. And sub-menus in the sidebar. As the one in : ikjensen.dk The menu you have is extremely unusable - even > in the browsers in which it works. For that type of menu you really should > be using a scripted one. Any suggestions in this direction. -- Regards / Mhv. Ib K. jensen __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Menu-issue
On 29/12/08 09:24, Ib Jensen wrote: > The menu you have is extremely unusable - even >> in the browsers in which it works. For that type of menu you really should >> be using a scripted one. > > Any suggestions in this direction. If you want something out of the box: * Ultimate Drop Down Menu: http://www.udm4.com/ * Yahoo! User Interface menu: http://developer.yahoo.com/yui/menu/ The fundamentals of keyboard accessibility here are reasonably straightforward. If submenus are to be accessible with the keyboard, ensure you can open, select, and close menu items with the keyboard. Using standard controls (buttons and links) with "click" handlers is an easy way to achieve this. Counter-intuitively any activation of a standard control (e.g. by pressing enter with the keyboard, by speaking the control name to speech recognition software, by pressing on a iPhone touchscreen) fires a 'click' event - it doesn't need to be a mouse. Alternately, you might choose to make top-menu items hub pages. In that case, you might choose to make the top-menu items simple links, with hover listeners attached to show dropdowns. That way, when used from the keyboard, you'd activate the links to go through to the hubpage and delve further into the website from there. Either way, ensure that "hidden" items either cannot be focused with the keyboard or are made visible on focus; it's crucial that users understand where focus is and what happens if (for example) they press Enter. (You'll likely want to track focus and blur events for this.) Personally, I'd avoid dropdowns for a content-driven website. I think it's better to keep the options presented to the user simple, relevant, and visible, rather than arrayed in all their complexity hidden behind functionality that varies from site to site. -- Benjamin Hawkes-Lewis __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Menu-issue
From: "Ib Jensen" > 2008/12/28 Al Sparber : >> From: "Ib Jensen" >>> 2008/12/28 David : > >> You would be better off with a nice single-level CSS menu across the top >> with sidebar context menus. > > You mean, just a single-level drop-down menu. And sub-menus in the > sidebar. > As the one in : ikjensen.dk Yes. That approach is more usable. > The menu you have is extremely unusable - even >> in the browsers in which it works. For that type of menu you really >> should >> be using a scripted one. > > Any suggestions in this direction. UDM: http://www.udm4.com/ PMM2: http://www.projectseven.com/products/menusystems/pmm2/ -- Al Sparber - PVII http://www.projectseven.com The Finest Dreamweaver Menus | Galleries | Widgets http://www.projectseven.com/go/pop The Ultimate DW Menu System __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Menu-issue
2008/12/29 >> Any suggestions in this direction. > > UDM: > http://www.udm4.com/ > > PMM2: > http://www.projectseven.com/products/menusystems/pmm2/ > > * Yahoo! User Interface menu: http://developer.yahoo.com/yui/menu/ Thanks to both of you for these links. The only problem are, I don't have Dreamweaver or anything like. So it must bee something like the Yahoo-thing, maybe. -- Regards / Mhv. Ib K. jensen __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] menu issue
Hi Ian, [quote] Although there is no change to the html, I have had to add an extra style code in the contact and portfolio pages as the menu sits a few pixels higher than does than it does on the other pages. [/quote] You are right it is a very odd one! After using Firebug and Webdeveloper toolbar the only issue I can see is that #left slightly overlaps the #content which may be forcing the UL down (depending on the content on the right hand side. Regards, ~Mx __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] menu issue
Ian Young wrote:
> http://db-studio.venus.titaninternet.co.uk/index.php
>
> Although there is no change to the html, I have had to add an extra
> style code in the contact and portfolio pages as the menu sits a few
> pixels higher than does than it does on the other pages.
Some pages have a Transitional doctype and others have a Strict doctype.
That explains the different handling of elements inside your h1, making
the h1 vary in height between pages.
Mode-stabilize the h1 construction first, by adding...
h1 * {display: block;}
h1 {padding-bottom: 6px;}
After that you should need no page specific styling of the nav-margin,
and can adjust the padding-bottom on h1 to taste to push the nav down.
regards
Georg
--
http://www.gunlaug.no
__
css-discuss [cs...@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] menu issue
> Cc: css-d@lists.css-discuss.org
> Subject: Re: [css-d] menu issue
>
> Ian Young wrote:
>
> > http://db-studio.venus.titaninternet.co.uk/index.php
> >
> > Although there is no change to the html, I have had to add an extra
> > style code in the contact and portfolio pages as the menu sits a few
> > pixels higher than does than it does on the other pages.
>
> Some pages have a Transitional doctype and others have a Strict
> doctype.
> That explains the different handling of elements inside your h1, making
> the h1 vary in height between pages.
Duh! Thanks. It had to be simple, but I hadn't appreciated how stupid I had
been.
>
> Mode-stabilize the h1 construction first, by adding...
>
> h1 * {display: block;}
> h1 {padding-bottom: 6px;}
>
> After that you should need no page specific styling of the nav-margin,
> and can adjust the padding-bottom on h1 to taste to push the nav down.
All looks they way it should now.
Thanks again.
Ian
__
css-discuss [cs...@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
