[WSG] IE incompatability
I'm having some browser incompatabilities - I can't get the nav bar to appear correctly. Here's the URL: http://studentweb.usq.edu.au/home/w0011373 (CSS at http://studentweb.usq.edu.au/home/w0011373/assets/css/main- style.css) I'm expecting popup submenus and the nav bar to be positioned in the middle of the nav container - it works fine in Firefox but is no good in IE or Opera (submenus OK in opera, but not the positioning). I've tried changing the text align code, but no luck. Any suggestions? This is my first attempt at a CSS page, so go easy on me :) ** 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] Online screen viewer
Thanks Patrick and Steven. If by Mac you mean OS X, rather than OS 9, have a look at this http://www.apple.com/downloads/macosx/unix_open_source/lynx.html The download link is broken, I'd been trying it since yesterday. I thought maybe server was down yesterday, but it looks more like the osxgnu.org site and its ftp no long exist. Testing in web based emulators is nice, but they usually can't emulate the interactive element (do forms work? same-page links like skip links? etc) Thanks for tips. Tee ** 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] Class Discusion: *{margin: 0; padding: 0} ???
Cole Kuryakin - x7m wrote:
So...will *{margin: 0 padding:0} in the HTML or Body declaration block zero
the margin and padding properties for all child elements in one go?
For all elements, yes (not just child elements, written like that).
I've
never seen the * used before.
It's called the universal selector:
http://www.w3.org/TR/CSS21/selector.html#universal-selector
--
Patrick H. Lauke
_
redux (adj.): brought back; returned. used postpositively
[latin : re-, re- + dux, leader; see duke.]
www.splintered.co.uk | www.photographia.co.uk
http://redux.deviantart.com
**
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] IE incompatability
[EMAIL PROTECTED] wrote: I'm having some browser incompatabilities - I can't get the nav bar to appear correctly. Here's the URL: http://studentweb.usq.edu.au/home/w0011373 (CSS at http://studentweb.usq.edu.au/home/w0011373/assets/css/main- style.css) I'm expecting popup submenus and the nav bar to be positioned in the middle of the nav container - it works fine in Firefox but is no good in IE or Opera (submenus OK in opera, but not the positioning). I've tried changing the text align code, but no luck. Any suggestions? This is my first attempt at a CSS page, so go easy on me :) You will need to use the sfhover fix for IE to show popup using active/hover. An example is here: http://www.tsbb.epsinick.co.uk/mainpage/index.php css here: http://www.tsbb.epsinick.co.uk/Assetts/Styles/tccbsuckerv.css This page uses to versions, one for vertical flyouts, one for horizantal. Please feel free to use what you want. Peter -- Peter Simons, Web Designer EpsiNick Productions [EMAIL PROTECTED] EpsiNick Productions hold all correspondence and contact details in confidence. Get Firefox!
Re: [WSG] Class Discusion: *{margin: 0; padding: 0} ???
Patrick H. Lauke wrote:
Cole Kuryakin - x7m wrote:
So...will *{margin: 0 padding:0} in the HTML or Body declaration
block zero
the margin and padding properties for all child elements in one go?
For all elements, yes (not just child elements, written like that).
Additionally, the universal selector has a specificity of zero, so
anything will override it.
**
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] Class Discusion: *{margin: 0; padding: 0} ???
On 6/17/05, Cole Kuryakin - x7m [EMAIL PROTECTED] wrote:
So...will *{margin: 0 padding:0} in the HTML or Body declaration block zero
the margin and padding properties for all child elements in one go? I've
never seen the * used before.
Something you may also want to remember is the immense advantage you
have with cross-browser issues. ULs have either margin or padding in
IE vs. Firefox, and there's more. Just bring it all back to zero and
you can style it your way without any surprises.
And if this will work, will it work with older browsers?
My most daring bet would be that even 4.0 browsers support the
universal selector.
--
Cheers,
Rob.
http://zooibaai.nl/ | http://digital-proof.org/
http://design.zooibaai.nl/ | More soon...
**
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] Followup to Tuesday's Brisbane Meeting
... and finally finds a few minutes to post! Tuesday's Brisbane meeting was great! Tania Lang of Peak Usability and the Brisbane CHI SIG dropped by to introduce herself and fill us in the SIG and World Usability Day on November 3 - sounds good. Brisbane is hosting a 1/2 day seminar entitled Usability: Making it Easy. Is anything happening local to you? Ben Buchanan of Griffith University (how cool is it to have the job title Web Standards Developer?) had the main gig, with his talk on Sticks, carrots staying sane: An approach to standards advocacy in large organisations and very interesting it was. The presentation is online at http://weblog.200ok.com.au/2005/06/sticks-carrots-staying-sane.html and the video appears to have been successful, so hopefully that will be available soon. August will see us avidly listening to John Bates talking to us about Internationalisation (geez, no wonder it is routinely abbreviated to 'i18n'!). warmly, Lea -- Core Group Member ** 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] Followup to Tuesday's Brisbane Meeting
On 17/06/2005, at 10:01 PM, Lea de Groot wrote: August will see us avidly listening to John Bates talking to us about Internationalisation (geez, no wonder it is routinely abbreviated to 'i18n'!). I've been told it's shortened for two reasons: Firstly, it's much easier to type. Secondly, it solves the internationalisation problem of isation vs ization :) Dean ** 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] Marking up lists with title
Hello, What is the recommended way to mark up a list that has a title? Normally I do: pFeatures:/p ul liIt's big/li liIt's heavy/li liIt's wood/li /ul Is there a better way to do that? Chris. ** 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] Marking up lists with title
Hi Chris, Personally I'd use a header of an appropriate level within the document. So: h1Document Title/h2 pBlah blah blah blah/p h2List Title/h2 ul liIt's big/li etc... /ul Cheers, Iain Chris W. Parker wrote: Hello, What is the recommended way to mark up a list that has a title? Normally I do: pFeatures:/p ul liIt's big/li liIt's heavy/li liIt's wood/li /ul Is there a better way to do that? Chris. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** 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] Marking up lists with title
What is the recommended way to mark up a list that has a title?
With better IE support, I might do:
ul title=Features
liIt's big/li
liIt's heavy/li
liIt's wood/li
/ul
...and then style it something like:
ul[title]:before {
display:block;
content:attr(title);
}
But, as it is, I suggest:
div
h1Features:/h1
ul
liIt's big/li
liIt's heavy/li
liIt's wood/li
/ul
/div
Replace h2 with 2,3,4,5,6 as appropriate. The only drawback to this, I
think, is that you are saying the heading is for the section, and the
section contains a list -- not that the heading is for the list.
--
Ben Curtis : webwright
bivia : a personal web studio
http://www.bivia.com
v: (818) 507-6613
**
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] Class Discusion: Centering a Fixed Width Layout
First, Firefox still allows the user to increase the font size if pixels are used. Second, font size is a much debated topic, and I think it's rather presumptious to infer that those of us who use pixels wallow in mediocrity. [EMAIL PROTECTED] wrote: I do teach the students about em, keywords and pixels, etc. based font size and allow them to make up their own minds. I understand the issue pertaining to accessibility and zooming text, but my personal preference is using pixels. Fair enough, it's your choice. But why make it more difficult for the user? Say to a user that you don't care if they read the text is a good way to loose return visitors. Admittedly, not many, as most people are used to putting up with the garbage that's out there; but why not rise above field, rather that wallowing the mediocrity? In general, if someone wants to resize the font, it's for a good reason. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** 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] Proper use of alt, title, longdesc
I'm trying to create easy-to-follow guidelines for my team. Regarding alt, title, and longdesc attributes for img tags, I'd like to know if my summary below could use some correcting. Also, URLs of concise guidelines on the matter would be appreciated. 1. When possible, images that are not part of the content (i.e., the user came to this page to view the content) should be placed in the CSS when possible. 2. ALL remaining img tags must have an alt attribute. 3. The alt text should be an empty string if the image conveys no information. 4. If the image has text in it, that text MUST be in the alt text. (Exception: CAPTCHAs) 5. If the image conveys information without words, compose a 1-5 word descriptive phrase to serve as an alternative to viewing the image, and use this as the alt text. Alternative does not mean descriptive; it means it serves the same purpose as the image. E.g., if the pictures help people identify people, use their names (Bob Downes, CFO), not description (man smiling in tweed suit). 6. If 5 words cannot convey the required information because details are important to understanding (e.g., a figure or illustration discussed in the accompanying text), use the longdesc attribute to link to a longer description of the image. 7. If additional information is desired (typically, meta information about the image, e.g., name of photographer), and does not need to be visible, use the title attribute. (Rare.) Regarding the longdesc, I read with interest the idea of longdesc footnotes, and may try to standardize on this. http://www.stuffandnonsense.co.uk/archives/accessibility_footnotes.html -- Ben Curtis : webwright bivia : a personal web studio http://www.bivia.com v: (818) 507-6613 ** 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] Online screen viewer
tee wrote: http://www.apple.com/downloads/macosx/unix_open_source/lynx.html The download link is broken, I'd been trying it since yesterday. I thought maybe server was down yesterday, but it looks more like the osxgnu.org site and its ftp no long exist. Works absolutely fine for me. Even cleared my cache and clicked the link again...so the site is definitely still there. -- Patrick H. Lauke _ redux (adj.): brought back; returned. used postpositively [latin : re-, re- + dux, leader; see duke.] www.splintered.co.uk | www.photographia.co.uk http://redux.deviantart.com ** 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] Marking up lists with title
Chris W. Parker wrote: pFeatures:/p ul liIt's big/li liIt's heavy/li liIt's wood/li /ul At the risk of sparking another cry of outrage and subsequent discussions, you could use the (badly defined) definition list construct instead: dl dtFeatures:/dt ddIt's big/dd ddIt's heavy/dd ddIt's wood/dd /dl P -- Patrick H. Lauke _ redux (adj.): brought back; returned. used postpositively [latin : re-, re- + dux, leader; see duke.] www.splintered.co.uk | www.photographia.co.uk http://redux.deviantart.com ** 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] Marking up lists with title
*Huge* fan as I am of definition lists, I fear this may be taking it just that little bit too far. ;) Chris is, after all, marking up a list title. A definition title and its subsequent definition suggests a much tighter and narrow scope than a general title gives. Whoops, here comes the massive and earnest discussion after all... Iain Patrick H. Lauke wrote: Chris W. Parker wrote: pFeatures:/p ul liIt's big/li liIt's heavy/li liIt's wood/li /ul At the risk of sparking another cry of outrage and subsequent discussions, you could use the (badly defined) definition list construct instead: dl dtFeatures:/dt ddIt's big/dd ddIt's heavy/dd ddIt's wood/dd /dl P ** 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] Proper use of alt, title, longdesc
Looks like a pretty good set of guidelines to me =). The stuff and nonsense foot notes idea is a good one, which also works for providing inline help instead of using pop-up windows. regards Terrence Wood. On 18 Jun 2005, at 6:07 AM, Ben Curtis wrote: I'm trying to create easy-to-follow guidelines for my team. Regarding alt, title, and longdesc attributes for img tags, I'd like to know if my summary below could use some correcting. Also, URLs of concise guidelines on the matter would be appreciated. 1. When possible, images that are not part of the content (i.e., the user came to this page to view the content) should be placed in the CSS when possible. 2. ALL remaining img tags must have an alt attribute. 3. The alt text should be an empty string if the image conveys no information. 4. If the image has text in it, that text MUST be in the alt text. (Exception: CAPTCHAs) 5. If the image conveys information without words, compose a 1-5 word descriptive phrase to serve as an alternative to viewing the image, and use this as the alt text. Alternative does not mean descriptive; it means it serves the same purpose as the image. E.g., if the pictures help people identify people, use their names (Bob Downes, CFO), not description (man smiling in tweed suit). 6. If 5 words cannot convey the required information because details are important to understanding (e.g., a figure or illustration discussed in the accompanying text), use the longdesc attribute to link to a longer description of the image. 7. If additional information is desired (typically, meta information about the image, e.g., name of photographer), and does not need to be visible, use the title attribute. (Rare.) Regarding the longdesc, I read with interest the idea of longdesc footnotes, and may try to standardize on this. http://www.stuffandnonsense.co.uk/archives/accessibility_footnotes.html -- Ben Curtis : webwright bivia : a personal web studio http://www.bivia.com v: (818) 507-6613 ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help ** ** 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] Marking up lists with title
Iain mailto:[EMAIL PROTECTED] on Friday, June 17, 2005 1:28 PM said: *Huge* fan as I am of definition lists, I fear this may be taking it just that little bit too far. ;) Chris is, after all, marking up a list title. A definition title and its subsequent definition suggests a much tighter and narrow scope than a general title gives. Whoops, here comes the massive and earnest discussion after all... Hmm... Yes I see what you're saying. However, since there seems to be no straight answer to this I'm inclined to think that any of the three given options would suffice. Thanks, Chris. ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
