Re: [WSG] Element suggestion requested
On 21/9/07 (10:39) Nick said: >Agreed that a heading doesn't really make much sense in this context. >Why not a rather than a ? That goes some way to addressing >the semantics of a list of statements, which is basically what this is. I the end, Nick, I plumped for a tag; it gives some semantic weight to the list item without implying a hierarchical structure. It's semantically ambiguous content, really, and I suspect that several tags *could* be pressed into service, so I'm not going to worry about it too much. I think that the most important aspect was defining it as a list; the secondary tag (strong) is less important IMHO. Also, this is destined for an intranet CMS that seems to view semantics and web standards largely as curiosities from the future to be marvelled over and then entirely ignored. Still, that's no reason for me not make the effort. (Their limited set up pull-down formatting options lacks yet still includes . Ugh). Thanks to everyone for your invaluable for your suggestions. -- Rick Lecoat *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Element suggestion requested
On 20 Sep 2007, at 20:55, Rick Lecoat wrote: On 20/9/07 (15:21) Nick said: Was there any particular reason not to have the h2 elements in the li elements, rather than placing them in a div? Um... a brain seizure of some sort I think. I somehow had it in my head that block-level items are not permitted inside list items, which is of course nonsense. But to be honest, even with the ability to put almost any tag inside an , I still don't feel like a heading is the right one. These aren't headings, after all. And a span probably isn't the right one either, but I chose it because its semantically neutral. These values should have some weight given to them, but H2 implies a hierarchical structure that is not there. Agreed that a heading doesn't really make much sense in this context. Why not a rather than a ? That goes some way to addressing the semantics of a list of statements, which is basically what this is. Regards, Nick. -- Nick Fitzsimons http://www.nickfitz.co.uk/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Element suggestion requested
On 20/9/07 (15:21) Nick said: >Was there any particular reason not to have the h2 elements in the li >elements, rather than placing them in a div? Um... a brain seizure of some sort I think. I somehow had it in my head that block-level items are not permitted inside list items, which is of course nonsense. But to be honest, even with the ability to put almost any tag inside an , I still don't feel like a heading is the right one. These aren't headings, after all. And a span probably isn't the right one either, but I chose it because its semantically neutral. These values should have some weight given to them, but H2 implies a hierarchical structure that is not there. Maybe a tag to replace the ? -- Rick Lecoat *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Element suggestion requested
Rick Lecoat wrote: Hi all. I've got a site which you can see a static screenshot of here (actually it's a screenshot of the photoshop file -- the site is still being coded) The item(s) I'm currently marking up is/are the 'Values' boxes in the right hand column, and I'm not really sure what element to use for the text. An h2 or something would convey the fact that they are considered important, but doesn't quite feel sematically 'right'. Whereas using a p makes it seem like just another bit of text like any other. Maybe they are a 'list' of values, and a ul/li would be best. Anyone have any suggestions? TIA ** off-list ** Rick, No comment on your question as it has already been answered. Fwiw, I would consider reducing the font-size in the right column as it is a little overwhelming and will be difficult to hold with font-sizing (unless, god forbid, that stuff will be an image of text in the final version). I /generally/ have a real problem with sites whose navigation (your left column) font-size is larger than the primary content-text (your center column). And your site is no different. Setting the primary content to user default (or close to it) and reducing the font-size used for the navigation is one way of overcoming this. Best, ~dL -- http://chelseacreekstudio.com/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Element suggestion requested
On 20 Sep 2007, at 11:56, Rick Lecoat wrote: On 19/9/07 (15:17) Kenny said: Yup. It's a list of values. Thanks for that Kenny. Even before posting the question I had started to code the 'Values' as a list, but then ran into difficulty styling it -- the vertically expandable box requires two images, and the tag only provides one hook to hang them on. Adding a span got me part way there, but there were still problems with the width, so I resorted to re-coding each as value as an h2 in a div. Your post prompted me to throw that away and go back to the unordered list, and to finally solve the styling problem, so thanks again. Was there any particular reason not to have the h2 elements in the li elements, rather than placing them in a div? Regards, Nick. -- http://www.nickfitz.co.uk/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Element suggestion requested
On 19/9/07 (15:17) Kenny said: >Yup. It's a list of values. Thanks for that Kenny. Even before posting the question I had started to code the 'Values' as a list, but then ran into difficulty styling it -- the vertically expandable box requires two images, and the tag only provides one hook to hang them on. Adding a span got me part way there, but there were still problems with the width, so I resorted to re-coding each as value as an h2 in a div. Your post prompted me to throw that away and go back to the unordered list, and to finally solve the styling problem, so thanks again. -- Rick Lecoat *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Element suggestion requested
> Maybe they > are a 'list' of values, and a ul/li would be best. Yup. It's a list of values. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] Element suggestion requested
Hi all. I've got a site which you can see a static screenshot of here (actually it's a screenshot of the photoshop file -- the site is still being coded) The item(s) I'm currently marking up is/are the 'Values' boxes in the right hand column, and I'm not really sure what element to use for the text. An h2 or something would convey the fact that they are considered important, but doesn't quite feel sematically 'right'. Whereas using a p makes it seem like just another bit of text like any other. Maybe they are a 'list' of values, and a ul/li would be best. Anyone have any suggestions? TIA -- Rick Lecoat *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***