Re: [WSG] Big Browsing Issues on clients PC Laptop AOL
Validate your CSS - there area few errors that may be to blame. >From the validator: URI : http://www.dianebrinker.com/styles.css 16 #contentProperty opacity doesn't exist in CSS level 2.1 but exists in [css3] : 0.8 17 #contentParse Error opacity=80) 303 #quotes_container Property opacity doesn't exist in CSS level 2.1 but exists in [css3] : 0.8 304 #quotes_container Parse Error opacity=80) 485 .menu Property opacity doesn't exist in CSS level 2.1 but exists in [css3] : 0.8 486 .menu Parse Error opacity=80) 566 #tabsI Property opacity doesn't exist in CSS level 2.1 but exists in [css3] : 0.8 567 #tabsI Parse Error opacity=80) URI : http://www.dianebrinker.com/menu.css -1 File not found: http://www.dianebrinker.com/menu.css: Not Found - Original Message - From: "Kristine Cummins" <[EMAIL PROTECTED]> To: wsg@webstandardsgroup.org Sent: Saturday, October 18, 2008 2:19:12 PM GMT -05:00 US/Canada Eastern Subject: [WSG] Big Browsing Issues on clients PC Laptop AOL I just launched a site, and it’s browsing fine on my PC & Mac laptop from IE5-8 browsers to FF etc. However, when my client visits her site on her PC laptop using AOL , it is browsing ( as if ) the stylesheet is applying only half way. I’ve recommended her to download the latest IE or FF, but she hasn’t done it yet. When she goes to her place of work, it looks fine. How could there be this huge discrepancy on her PC Laptop using AOL? Site is www.dianebrinker.com Screenshots she sent me: http://www.dianebrinker.com/diane_screenshots.jpg Thanks in advance for any help! Kristine *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] labels as input wrappers + in place of legend
- Original Message - From: "Jason Grant" <[EMAIL PROTECTED]> "Boots.com is one of the most 'formsy' web sites out there. I suggest you sign up for it and try to see what has been done there..." Regards. boots.com redirects to "bootsus.bri-global.com/" - is this the site you were referring to? Looks OK, but uses questionalble extra , lacks / and/or , and no indication of required fields. Also, erors out when attemptingto submit the form for "new user" The "leftformcell" and "rightformcell" definitey provide a lot of flexibility, but is questionably overboard vs. applying . I had not thought about creating two seperate wrappers...trying to get it done with one or less. I am close to having a version 1 to post for review...I may do two different approaches to look for better feedback - Pro vs. Cons for each approach. Thanks. *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] labels as input wrappers + in place of legend
- Original Message - From: "Jason Grant" <[EMAIL PROTECTED]> To: wsg@webstandardsgroup.org Sent: Friday, October 17, 2008 4:51:46 AM GMT -05:00 US/Canada Eastern Subject: Re: [WSG] labels as input wrappers + in place of legend You should also be aware of the fact that for a commercial project the below code snippet you posted will not be sufficient, as it does not have enought styling/behavioural hooks in it... -- That's my next bone to pick, and why I really liked the wrapper. I really dislike the idea of wrapping the & in a but I will likely have to for the exact point you have made. I need lots of flexibility but want minimal code bloat. Here's a simplified version of where I am heading: ... Contact Information Name Name Date of Birth Month Day Day ... Why the in the ? I may potentially need to style that area as a sliding doors tab, plus it seems easier to achieve consistent cross-browser styles on the span as opposed to the . The nested is to allow for the DOB to me horizontal if/when desired. Still lots to do regarding other form elements...more questions as I progress. I will also post an example. Thanks thus far! Seems painfully blaoted to me, but I need a lot of control to match virtually any situation *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] labels as input wrappers + in place of legend
Thank you everyone for your replies. So it seems the trusty old traditional Contact Information Name is the way to go to keep all browsers and screen readers happy. I think I can likely lose the and replace that with a display: block; on the label or input. This is the first of a series of questions I will have. I have the opportunity to rewrite some extremely complex forms for a very large CMS and I want to make them the best they can be. Thanks! - Original Message - From: "Mike at Green-Beast.com" <[EMAIL PROTECTED]> To: wsg@webstandardsgroup.org Sent: Thursday, October 16, 2008 11:07:33 AM GMT -05:00 US/Canada Eastern Subject: Re: [WSG] labels as input wrappers + in place of legend Hi Ben, > I've always used label arount input fields [...] > I don't think I've ever seen any recommendation against it. Here's one for you: http://green-beast.com/blog/?p=254 I haven't been paying attention to this, and someone's probably already said it (if so, sorry), but it's also worth noting that only form elements will be read in a screen reader's forms mode. Being as such, it's better to style the legend to look like an h6 rather than substituting it for one. Respectfully, Mike Cherim *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *** *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] labels as input wrappers + in place of legend
I am looking for feedback on two questions, based on the simple form snippet below. Personal Details Name: ID Number: Question 1: Is it acceptable, or advisable, to use a header tag in place of the in order to get cross-browsers consistency when dealing with complex form styling? How much impact might this have on accessibility, if any? Question 2: I don't see many folks using the as a wrapper to contain the input. Any reason not to do this? It allows for the to be removed via display: block; on the tag as well as allowing users (of most browsers) to click on a much larger label to select the accompanying input. Personal Details Name: ID Number: *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
