Re: [WSG] Browser restrictions
At 08:55 26/03/2004 +1000, you wrote: I don't know if this question gets recycled often here, I'm very new... What I'd like to know is if there's a good resource that shows browser restrictions as far as CSS compatability goes. This is an excellent collection of CSS resource links: http://www.thenoodleincident.com/tutorials/css/index.html He branches browser-related ones out here: http://www.thenoodleincident.com/tutorials/css/browsers.html Netscape host some commonly-used compatibility charts: http://devedge.netscape.com/library/xref/2003/css-support/ More generally, these are excellent CSS resources: css-discuss Wiki http://css-discuss.incutio.com/ CSS filters and hacks http://www.dithered.com/css_filters/index.html (includes full browser compatibility details for each filter/hack technique) HTH, Gyrus [EMAIL PROTECTED] http://norlonto.net/gyrus/dev/ PGP key available * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
Re: [WSG] Opera 7 problem with horizontal nav list
At 15:11 23/03/2004 +0100, you wrote: G It's a shame if floated lis all stack up in Opera but inline lis lose G padding in IE5.0. Ah well... Just a quick guess, but have you removed the display:block? Yeah, it's all inline now. I was just making a general comment there about the fact that display:block/float screws Opera but display:inline screws IE5.0/Win. In the end I've plumped for the one that screws IE5.0/Win - even though it's a more popular browser, the problem isn't as severe as Opera. It's ugly, but accessible. The problem in Opera made the nav links completely unusable. cheers, Gyrus [EMAIL PROTECTED] http://norlonto.net/gyrus/dev/ PGP key available * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
Re: [WSG] Opera 7 problem with horizontal nav list
At 15:22 23/03/2004 +0100, you wrote: Was to quick on my previous post: have you tried using margin instead of padding? Or adding a position:relative to let IE5 behave? Just still guessing... Appreciated. I think the reason for padding rather than margin is so the space created is (1) filled with the background colour and (2) clickable. I'll experiment with position:relative. Gyrus [EMAIL PROTECTED] http://norlonto.net/gyrus/dev/ PGP key available * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
Re: [WSG] tab navigation in CSS
At 14:38 23/03/2004 -0500, you wrote: I'm wondering if anyone on this list could direct me to an example of a good tab navigation bar done in CSS. I want to create something similar to the navigation on Amazon.com or apple.com -- in CSS, of course. Doug Bowman's Sliding Doors technique is a good place to start: http://alistapart.com/articles/slidingdoors/ http://alistapart.com/articles/slidingdoors2/ HTH, Gyrus [EMAIL PROTECTED] http://norlonto.net/gyrus/dev/ PGP key available * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
Re: [WSG] Opera 7 problem with horizontal nav list
At 01:52 22/03/2004 +0100, you wrote: G I'm floating the li elements left, Do they have to be floated? Why not using display:inline? That way the li are forced onto 1 line. I think the reasons I used float were: - Making the a display: block seemed to give me better control over padding (especially in IE5/Win) - If the a is a block, the li can't really be inline (can it?) I've changed the list to use display: inline instead (http://headoverheels.org.uk/). This made the borders I applied to li not work properly, so I've had to remove them just to try and iron out the other problems: - In IE5.0/Win, the padding doesn't apply to the the a - In all browsers I've looked at, there's a bit of space between each li, with the background showing through (I want the lis flush against each other) Any ideas? thanks, Gyrus [EMAIL PROTECTED] http://norlonto.net/gyrus/dev/ PGP key available * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
Re: [WSG] Opera 7 problem with horizontal nav list
At 16:56 22/03/2004 +0100, you wrote: G - In IE5.0/Win, the padding doesn't apply to the the a Sorry, IE5.0 is something i'm no expert in I'm sure it seemed like an OK browser 3 years ago ;-) G - In all browsers I've looked at, there's a bit of space between each li, G with the background showing through (I want the lis flush against each other) If i understand it correctly, you have white space between your li. You can get them flush with a negative margin-right. Ah! Thanks, I'd forgotten about inline whitespace. It works OK in Opera now, but all padding is lost in IE5.0/Win. I've added some server-side hacks to just include the whitespace for this browser (maybe conditional comments would be better...) - otherwise the nav links all run together. It's a shame if floated lis all stack up in Opera but inline lis lose padding in IE5.0. Ah well... I've ditched the borders. The only problem now is... no, I'll leave it there. I think I'll set to it with a fresh mind tomorrow ;-) Gyrus [EMAIL PROTECTED] http://norlonto.net/gyrus/dev/ PGP key available * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
[WSG] Opera 7 problem with horizontal nav list
Hi, I'm working on a new site for a friend, and I'm having trouble getting the horizontal nav list working in Opera (7/Win). HTML: http://headoverheels.org.uk/index.html CSS: http://headoverheels.org.uk/css/screen.css (the design's still being done, ignore scrappiness ;-) I'm floating the li elements left, and they contain a tags set to display: block. It all works fine in Moz / IE5-6, but Opera 7 stack the lis on top of each other. Also, there's a big gap between the footer and the content that doesn't appear with other browsers. Anyone know Opera's quirks enough to help here? Gyrus [EMAIL PROTECTED] http://norlonto.net/gyrus/dev/ PGP key available * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
RE: [WSG] transitional, accessible popups?
At 16:55 18/03/2004 +, you wrote:
Change
onclick=window.open('index.cfm?id=23',
to
onclick=window.open(this.href,
Excellent!
thanks,
Gyrus
[EMAIL PROTECTED]
http://norlonto.net/gyrus/dev/
PGP key available
*
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list getting help
*
Re: [WSG] transitional, accessible popups?
At 18:06 18/03/2004 +0100, you wrote: It's quite fine, IMO. You should consider however making it a little less mouse-centric by adding a onkeypress event that does just the same than onclick. That would ask then for abstracting the code to a funcion and maybe rewording the title of the link Sorry about the nit-picking :-) Sure, I've not got round to getting onclick vs. onkeypress clear in my head - I'll use this opportunity to do so :-) As for the no-function JS and the title, they were just in there for demo purposes ;-) cheers, Gyrus [EMAIL PROTECTED] http://norlonto.net/gyrus/dev/ PGP key available * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
Re: [WSG] A rave about h1's
At 07:35 18/03/2004 +1100, you wrote: I've been thinking about a post from a few days ago that has been bothering me. The comments in this post highlight the difference between valid markup and structurally-sound markup: Question: ...you have the headings of these as h1s I'm not sure if you should have more than one h1 a page? is that correct? Reply: You can have as many h1's as you want From a valid code point of view, this is correct. Your page can be littered with h1 elements. But what about from a document-structure point of view? I often wonder about the possibility that a page might need more than one H1. I normally think of H1 as the title of the document. But, web pages being what they are, sometimes there might be a heading down a page that seems to require as much weight as the initial H1. Technically this should be another document, but sometimes client specs don't tally ;) Even so, structurally speaking, what about headings in sidebars? If you use H2, H3, or something like that, when you run your page through the nice W3C document structure engine, it looks like your sidebar stuff is specifically related to your content with the H1 (depending on which order you've got your DIVs in, I guess). Should we use H1 for a sidebar, to demarcate it as separate in structural terms from the main content, and style it with CSS? Does this impact any lo-fi visual devices (i.e. H1 default size being too big for these lesser page elements)? I suppose this is where XHTML 2(?) comes in with its SECTION tag, which enables dynamic heading levels. Or does it? Are web pages still seen within the document concept, where everything in them is a singular entity - whereas in real terms, we have global page sections, like sidebars, that aren't necessarily related to our main content in any structural way. A related area is the use of the TITLE tag. If H1 = document title, what about TITLE?! I saw someone refer to the TITLE tag as H0, which is neat, except: should H1 contain the same text as TITLE? If not, what's the difference? Wow, I didn't know I had that many questions! ;) Gyrus [EMAIL PROTECTED] http://norlonto.net/gyrus/dev/ PGP key available * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
Re: [WSG] A rave about h1's
At 07:35 18/03/2004 +1100, you wrote: I've been thinking about a post from a few days ago that has been bothering me. The comments in this post highlight the difference between valid markup and structurally-sound markup: Some more thoughts after a chat with a friend here: - Web pages can theoretically contain more than one document. Each document would have its own H1. - Therefore, in most pages, the TITLE would be the same as the H1 - unless there's more than one H1, in which case you'd have something like Three essays by George Orwell for the TITLE, and H1's for each essay. - Sidebars and their ilk would properly speaking need their own H1's (and possibly H2's). - In a sense, a H1 in a web page signals the start of a new document, or independent section of the page. I don't know how this tallies with XHTML 2 and the SECTION tag - anyone? Gyrus [EMAIL PROTECTED] http://norlonto.net/gyrus/dev/ PGP key available * The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help *
