Re: [WSG] Controling Windows DPI settings
On 2008/02/23 18:14 (GMT-0800) Hayden's Harness Attachment apparently typed: I have Windows Vista Home Premium and use 96 DPI. I am told repeteated ly that my fonts are to large. Probably you should offer example URLs of pages about which that complaint is made. I have even tried font-size: 80%; in my CSS and still get told the fonts are to large. All pages on which such CSS is used produces too small text in my browsers. I know you are not able to overide a person's preferences. can I do something in CSS to change the default DPI and/or font-size? And then create different CSS files to increase the DPI and/or font-sizes? Real DPI is a function of the combination of display size, and the actual resolution used. Windows defaults to (assumes) 96 DPI regardless of display size or resolution, but in recent years the manufacturers have been presetting their higher resolution Windows models with a just as arbitrary 120 instead of 96. The upshot is there is nothing about DPI that you can or should want to do anything about, except for the displays you have physical control over. The best thing you can do when anyone complains about text size in your web pages is point out that their browser defaults can be adjusted so suit their tastes, and explain that there are too many possible variations on local environments for you to assume anything other than a 100% of default text size base for your pages makes any logical sense. Those using modern browsers have a feature that enables visitors to select from among optional stylesheets, so you do have the means to cater to users who can't be bothered to suitably adjust their own environments to suit their own needs. Whether you can justify spending the time to use that function only you can answer, but if you use a lot of low contrast, wild colors, or small text, it's probably a really good idea to include alternative stylesheets with more conservative colors and/or other text size options. -- For God so loved the world that he gave his one and only Son, that whoever believes in him shall not perish but have eternal life. John 3:16 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] Site review - alachua co library
On 2008/02/27 18:39 (GMT+1100) John Hancock apparently typed: Here's a screenshot of a typical moderately high resolution environment: http://mrmazda.no-ip.com/SS/SC/sc-alaclib1.jpg and the setup source: http://mrmazda.no-ip.com/tmp/sc-alaclib1.html Just a thought, but a moderately high resolution environment to me is a setup of over 3mpx. For instance, dual 20 TFTs, dual 19 CRT or single 30 etc. A high resolution environment for me is about 7.5mpx. While I'm aware that your mileage may vary, a 1680 x 1200 pixel screen size is certainly not a standard one! I was hoping anyone who noticed that would just ignore it. I don't use flat panel displays, because they are just not suited to alternative screen resolutions desirable for thorough testing. What you see there in 1680x1200 is a virtual resolution, while the screenshot itself is exactly the fullscreen px size of typical 22 desktop displays now common in stores, and of typical 16 17 laptops. The actual physical resolution is UXGA 1600x1200, with an 80px wide virtual addition. On Linux, nearly any virtual resolution is possible without fancy hardware or additional software. :-) Thus I'm really curious about your definition of a standard one! The standard LCDs now commonly available at retail new are: XGA 1024x768 (4:3) (slightly low, usually 15) SXGA 1280x1024 (5:4) (standard or base, almost exclusively 17 or 19) WXGA 1280x800 (16:10) (standard or base, 11.1 to 15.4) SXGA+ 1400x1050 (4:3) (standard or base, 20) WXGA+ 1440x900 (16:10) (slightly high, 16 to 21) WSXGA+ 1680x1050 (16:10) (moderately high, 16 to 23) UXGA 1600x1200 (4:3) (high, 20 to 22) WUXGA 1920x1200 (16:10) (high, 16 to 27) Naturally the meanings vary according to whether desktop or laptop, as the average PPI for laptops is much higher than for desktops, which is why the common 120 DPI replacement for 96 DPI is provided by laptop OEMs. The Standard Panels Working Group (SPWG) isn't the fastest moving of organisations, admittedly, but you'll find that they're usually ratifying 16:10 aspect ratios as standard - something to consider when designing sites. Additionally, those of us with extremely large working areas should usually have a 17 TFT or lower to test on for 'the great unpixeled'. Or a large CRT and a small CRT, which can provide the utility of at least 3 LCDs - each! Most panels just don't have usable optional resolutions. -- For God so loved the world that he gave his one and only Son, that whoever believes in him shall not perish but have eternal life. John 3:16 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
[WSG] input type=submit and IE6 and 7
Does anyone know why in IE6 and 7 there is a black outline around buttons that use input type=submit instead of input type=button, and is there a work around to rid of the outline? Webaim.org suggests using 'submit' or 'reset' instead of 'button' to define the input type. http://www.webaim.org/techniques/forms/controls#button Would input type=button be just as accessible? Thanks in advance Nancy Johnson *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] input type=submit and IE6 and 7
Hi Nancy, the reason for the black outline around the submit button in IE6 and 7 is that IE renders the buttons with the system API, and if you view each Windows interface, the default button that fires the click event with the enter too is outlined black. I think that It would not be at any accessible to make the submit button ( input type=submit ) with a (input type=button ) because you have the issue of how you make the submit? Via Javascript? And if Javascript is disabled? Cheers. -- Diego La Monica (IWA/HWG) Web: programmazione, standards, accessibilità e 2.0 W3C Protocols and Format Working Group member for IWA/HWG Web Skill Profiles WG Member (http://skillprofiles.eu ) email: [EMAIL PROTECTED] - Skype: diego.la.monica mobile +393337235382 - Web: http://diegolamonica.info - http://jastegg.it [ Le uova si sono schiuse! ] On 27/02/2008, Nancy Johnson [EMAIL PROTECTED] wrote: Does anyone know why in IE6 and 7 there is a black outline around buttons that use input type=submit instead of input type=button, and is there a work around to rid of the outline? Webaim.org suggests using 'submit' or 'reset' instead of 'button' to define the input type. http://www.webaim.org/techniques/forms/controls#button Would input type=button be just as accessible? Thanks in advance Nancy Johnson *** 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] multiple css style sheets
Just inherited a site and saw pages with multiple style sheets. Is there a reason for that and how does the browser determine what to use if there is a conflict -- Michael Horowitz Your Computer Consultant http://yourcomputerconsultant.com 561-394-9079 *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] multiple css style sheets
On 27 Feb 2008, at 16:55, Michael Horowitz wrote:
Just inherited a site and saw pages with multiple style sheets. Is
there a reason for that and how does the browser determine what to
use if there is a conflict
Michael, I assume that you mean that the page referenced several
external stylesheets using multiple link tags?
I /believe/ that the browser simple loads them one after the other in
the order that they appear in the source (unless the stylesheet's rel
is marked up as being 'alternate'), with one stylesheet being
appended to the end of the previous one. In effect the browser sees
one big stylesheet.
As for conflict resolution, my understanding is that the normal rules
of CSS inheritance apply.
Eg.
You have source:
link rel=stylesheet type=text/css href=styles_A.css /
link rel=stylesheet type=text/css href=styles_B.css /
link rel=stylesheet type=text/css href=styles_C.css /
In the CSS:
styles_A contains the rule:
body { background-color: white}
...and...
styles_B contains the rule:
body { background-color: red}
then the page's background colour would, rather unpleasantly, be red.
I think that's right...
--
Rick Lecoat
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
Re: [WSG] multiple css style sheets
You specify different stylesheets for different medias. The most common ones are to target handhelds, print and screenreaders. The user-agent will use the MEDIA attribute to pick the correct stylesheet. It is also possible to provide multiple stylesheets which the user can select from. Though IE doesn't have any UI for this. These are provided by adding 'alternate' to the REL property. ( rel=alternate stylesheet ) - Original Message - From: Michael Horowitz [EMAIL PROTECTED] To: wsg@webstandardsgroup.org Sent: Wednesday, February 27, 2008 5:55 PM Subject: [WSG] multiple css style sheets Just inherited a site and saw pages with multiple style sheets. Is there a reason for that and how does the browser determine what to use if there is a conflict -- Michael Horowitz Your Computer Consultant http://yourcomputerconsultant.com 561-394-9079 *** 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] multiple css style sheets
I see no reason not to use multiple stylesheets other than a smaller download time. Each stylesheet should be separated only if it serves a purpose of course. For example, most of my sites currently use this formula: !-- CSS -- link rel=stylesheet type=text/css media=all href=/css/global.css link rel=stylesheet type=text/css media=screen, projection href=/css/screen.css link rel=stylesheet type=text/css media=screen, projection href=/css/homepage.css !--[if lt IE 7] link rel=stylesheet type=text/css media=screen, projection href=/css/ie.css ![endif]-- link rel=stylesheet type=text/css media=print href=/css/print.css I could probably add a handheld stylesheet to that setup. The global stylesheet handles the global styles for all media types and performs some resets to standardize areas where browsers differ. The screen stylesheet handles the universal screen styles. The homepage stylesheet handles elements that are unique to the homepage. (or subpage if thats the case) The ie stylesheet handles box model fixes etc for ie6 and under Finally, the print stylesheet handles print display. Needless to say, one stylesheet couldn't be this flexible. As far as conflicting rules, typically the browser would render whichever rule came last, overwriting any previously set styles while inheriting those that are not affected. Joseph R. B. Taylor /Designer / Developer/ -- Sites by Joe, LLC /Clean, Simple and Elegant Web Design/ Phone: (609) 335-3076 Fax: (866) 301-8045 Web: http://sitesbyjoe.com Email: [EMAIL PROTECTED] Michael Horowitz wrote: Just inherited a site and saw pages with multiple style sheets. Is there a reason for that and how does the browser determine what to use if there is a conflict *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***begin:vcard fn:Joseph Taylor n:Taylor;Joseph org:Sites by Joe, LLC adr:;;408 Route 47 South;Cape May Court House;NJ;08210;USA email;internet:[EMAIL PROTECTED] title:Designer / Developer tel;work:609-335-3076 tel;fax:866-301-8045 tel;cell:609-335-3076 x-mozilla-html:TRUE url:http://sitesbyjoe.com version:2.1 end:vcard
[WSG] Linux Page Test Please
Good Linux users: Can I ask you to take this page for a spin and reply off-list if you encounter a problem? http://allturf.sitesbyjoe.com/ Thanks! -- Joseph R. B. Taylor /Designer / Developer/ -- Sites by Joe, LLC /Clean, Simple and Elegant Web Design/ Phone: (609) 335-3076 Fax: (866) 301-8045 Web: http://sitesbyjoe.com Email: [EMAIL PROTECTED] *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***begin:vcard fn:Joseph Taylor n:Taylor;Joseph org:Sites by Joe, LLC adr:;;408 Route 47 South;Cape May Court House;NJ;08210;USA email;internet:[EMAIL PROTECTED] title:Designer / Developer tel;work:609-335-3076 tel;fax:866-301-8045 tel;cell:609-335-3076 x-mozilla-html:TRUE url:http://sitesbyjoe.com version:2.1 end:vcard
RE: [WSG] Screen Standards - was alachu
Hi David, There are actually standard screen sizes, which is why screens like HP's 1280x768 14 screen and Apple's 15 screen were retired quietly. They were new and different, then different, then became non-standard when 14.1 and 15.4 devices preserved a 16:10 aspect ratio. The manufacturers of LCD (and CRT) panels have been sitting down and working out what sizes they should all work to, to make things easy, predominantly, for gaming and windows driver manufacturers. And they've been doing this for about 15 years or so - so there are standards. That there isn't a 'standard' screen size is agreed in terms of 'everyone uses a different screen', but that's why we all seem to design to the lowest (common) common denominator, whatever our definition of that is. In terms of internet browsing, many professionals have been using the HTC devices for a while, such as the Universal, TyTn etc. These typically have 320x240 (either aspect) or 640x480 screens and as such some websites really struggle - alistapart is a great example of one. Many seem to be of the opinion that these screen sizes don't matter at all in terms of design - my method is usually to build a /mobile site for mobile users. John. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Hucklesby Sent: Thursday, 28 February 2008 4:41 AM To: wsg@webstandardsgroup.org Subject: Re: [WSG] Site review - alachua co library On Wed, 27 Feb 2008 03:42:07 -0500, Felix Miata wrote: On 2008/02/27 18:39 (GMT+1100) John Hancock apparently typed: Just a thought, but a moderately high resolution environment to me is a setup of over 3mpx. For instance, dual 20 TFTs, dual 19 CRT or single 30 etc. A high resolution environment for me is about 7.5mpx. While I'm aware that your mileage may vary, a 1680 x 1200 pixel screen size is certainly not a standard one! [...] Thus I'm really curious about your definition of a standard one! There is clearly no standard screen size or resolution, despite assumptions too often made by designers. Please consider that the web is no longer only available on PCs. I read recently that 30-40% of Internet traffic in Europe comes from mobile phones. There are hand-held devices, game boxes, and doubtless more to come as well. The advent of the iPhone in N. America is already changing Internet browsing habits over here. I agree with Felix that we should get away from the idea that CSS can deliver a better experience by significantly changing the text size. FWIW my 15 laptop display is 1400 x 1050 running at 120 DPI. With large fonts I find the defaults very comfortable. I use Opera as my default browser, so text delivered as 10 pixels is easily increased. Age seems relevant to some who discuss this issue, for some reason I can't fathom, so I'll mention that I am 72. Cordially, David -- *** 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] multiple css style sheets
Hi ,
How do browsers determine the winner in a conflict... well, AFAIK, they
take the first style that is most relevant to the element.
That would be the LAST style that is most relevant to the element. (unless
!important is used to override the cascade.)
It also worth noting that multiple stylesheets are also commonly
referenced within CSS using @import.
The main benefit of using multiple stylesheets is for modular code.
Kind Regards,
Kane Tapping
Web Standards Developer
Web and Content Management Services
Griffith University. 4111. Australia.
[EMAIL PROTECTED]
Phone: +61 (0)7 3735 7630
Steven Workman [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
28/02/2008 03:36 AM
Please respond to
wsg@webstandardsgroup.org
To
wsg@webstandardsgroup.org
cc
Subject
Re: [WSG] multiple css style sheets
Michael,
Multiple style sheets are quite common in large sites. Splitting your
stylesheets into a basics, main and special cases is good for
keeping your code separate, also allowing multiple developers to work on
different areas of a site's styles without interrupting each other. It's
also becoming more common that any off the shelf javascript techniques
come with their own stylesheets i.e. Cody Lindley's Thickbox.
How do browsers determine the winner in a conflict... well, AFAIK, they
take the first style that is most relevant to the element.
Say you had ullispan class=bobSome text/span/li/ul
If your first stylesheet said:
ul li { color:red;
}
and the second one said
.bob { color: blue;
}
It would render as blue.
However, if the first one said
ul li .bob { color:red;
}
and the second one remained the same
.bob { color: blue;
}
It would render as red
Steve Workman
PA Consulting Group
www.paconsulting.com
[EMAIL PROTECTED]
www.steel-software.com
On 27/02/2008, Michael Horowitz [EMAIL PROTECTED]
wrote:
Just inherited a site and saw pages with multiple style sheets. Is
there a reason for that and how does the browser determine what to use
if there is a conflict
--
Michael Horowitz
Your Computer Consultant
http://yourcomputerconsultant.com
561-394-9079
***
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]
***
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
Re: [WSG] multiple css style sheets
Is there a difference or specific reason to use the @import
Michael Horowitz
Your Computer Consultant
http://yourcomputerconsultant.com
561-394-9079
Kane Tapping wrote:
Hi ,
How do browsers determine the winner in a conflict... well, AFAIK,
they take the first style that is most relevant to the element.
That would be the LAST style that is most relevant to the element.
(unless !important is used to override the cascade.)
It also worth noting that multiple stylesheets are also commonly
referenced within CSS using @import.
The main benefit of using multiple stylesheets is for modular code.
Kind Regards,
Kane Tapping
Web Standards Developer
Web and Content Management Services
Griffith University. 4111. Australia._
[EMAIL PROTECTED] mailto://[EMAIL PROTECTED]/
Phone: +61 (0)7 3735 7630
*Steven Workman [EMAIL PROTECTED]*
Sent by: [EMAIL PROTECTED]
28/02/2008 03:36 AM
Please respond to
wsg@webstandardsgroup.org
To
wsg@webstandardsgroup.org
cc
Subject
Re: [WSG] multiple css style sheets
Michael,
Multiple style sheets are quite common in large sites. Splitting your
stylesheets into a basics, main and special cases is good for
keeping your code separate, also allowing multiple developers to work
on different areas of a site's styles without interrupting each other.
It's also becoming more common that any off the shelf javascript
techniques come with their own stylesheets i.e. Cody Lindley's Thickbox.
How do browsers determine the winner in a conflict... well, AFAIK,
they take the first style that is most relevant to the element.
Say you had ullispan class=bobSome text/span/li/ul
If your first stylesheet said:
ul li { color:red;
}
and the second one said
.bob { color: blue;
}
It would render as *blue*.
However, if the first one said
ul li .bob { color:red;
}
and the second one remained the same
.bob { color: blue;
}
It would render as *red
*
Steve Workman
PA Consulting Group_
__www.paconsulting.com_ http://www.paconsulting.com/_
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]_
__www.steel-software.com_ http://www.steel-software.com/
On 27/02/2008, *Michael Horowitz*
[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Just inherited a site and saw pages with multiple style sheets. Is
there a reason for that and how does the browser determine what to use
if there is a conflict
--
Michael Horowitz
Your Computer Consultant_
__http://yourcomputerconsultant.com_ http://yourcomputerconsultant.com/
561-394-9079
***
List Guidelines: _http://webstandardsgroup.org/mail/guidelines.cfm_
Unsubscribe: _http://webstandardsgroup.org/join/unsubscribe.cfm_
Help: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
***
***
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]
***
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***
RE: [WSG] multiple css style sheets
On Behalf Of Kane Tapping Sent: Wednesday, February 27, 2008 6:25 PM To: wsg@webstandardsgroup.org Subject: Re: [WSG] multiple css style sheets How do browsers determine the winner in a conflict... well, AFAIK, they take the first style that is most relevant to the element. That would be the LAST style that is most relevant to the element. (unless !important is used to override the cascade.) rules with greater specificity will override the cascade too -- Regards, Thierry | http://www.TJKDesign.com *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] multiple css style sheets
To be a little pedantic, the cascade includes both of those things so it's incorrect to say they override the cascade. My understanding of the cascade is that it includes all the following steps: 1. Sort by importance (i.e. !important or not) 2. Sort by specificity 3. Sort by source order That is, the 'cascade' represents this whole process of resolution. On 28/02/2008, at 3:03 PM, Thierry Koblentz wrote: That would be the LAST style that is most relevant to the element. (unless !important is used to override the cascade.) rules with greater specificity will override the cascade too -- Andrew http://tetlaw.id.au *** List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] ***
Re: [WSG] multiple css style sheets
Hi ,
I believe @import was originally used by designers to create styles
Netscape Navigator 4 would not implement incorrectly.
Some other reasons why you might use this rather then multiple link rel
declarations, include:
You can declare the @import within a CSS file style or style= (you can
also choose where in the CSS document to @import, allowing greater control
of the cascade's.)
link rel can only be declared in the head of a document (some systems do
not give access to this area, or only allow a set link to their
stylesheet.)
Kind Regards,
Kane Tapping
Web Standards Developer
Web and Content Management Services
Griffith University. 4111. Australia.
[EMAIL PROTECTED]
Phone: +61 (0)7 3735 7630
Michael Horowitz [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
28/02/2008 01:46 PM
Please respond to
wsg@webstandardsgroup.org
To
wsg@webstandardsgroup.org
cc
Subject
Re: [WSG] multiple css style sheets
Is there a difference or specific reason to use the @import
Michael Horowitz
Your Computer Consultant
http://yourcomputerconsultant.com
561-394-9079
Kane Tapping wrote:
Hi ,
How do browsers determine the winner in a conflict... well, AFAIK,
they take the first style that is most relevant to the element.
That would be the LAST style that is most relevant to the element.
(unless !important is used to override the cascade.)
It also worth noting that multiple stylesheets are also commonly
referenced within CSS using @import.
The main benefit of using multiple stylesheets is for modular code.
Kind Regards,
Kane Tapping
Web Standards Developer
Web and Content Management Services
Griffith University. 4111. Australia._
[EMAIL PROTECTED] mailto://[EMAIL PROTECTED]/
Phone: +61 (0)7 3735 7630
*Steven Workman [EMAIL PROTECTED]*
Sent by: [EMAIL PROTECTED]
28/02/2008 03:36 AM
Please respond to
wsg@webstandardsgroup.org
To
wsg@webstandardsgroup.org
cc
Subject
Re: [WSG] multiple css style sheets
Michael,
Multiple style sheets are quite common in large sites. Splitting your
stylesheets into a basics, main and special cases is good for
keeping your code separate, also allowing multiple developers to work
on different areas of a site's styles without interrupting each other.
It's also becoming more common that any off the shelf javascript
techniques come with their own stylesheets i.e. Cody Lindley's Thickbox.
How do browsers determine the winner in a conflict... well, AFAIK,
they take the first style that is most relevant to the element.
Say you had ullispan class=bobSome text/span/li/ul
If your first stylesheet said:
ul li { color:red;
}
and the second one said
.bob { color: blue;
}
It would render as *blue*.
However, if the first one said
ul li .bob { color:red;
}
and the second one remained the same
.bob { color: blue;
}
It would render as *red
*
Steve Workman
PA Consulting Group_
__www.paconsulting.com_ http://www.paconsulting.com/_
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
_
__www.steel-software.com_ http://www.steel-software.com/
On 27/02/2008, *Michael Horowitz*
[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Just inherited a site and saw pages with multiple style sheets. Is
there a reason for that and how does the browser determine what to use
if there is a conflict
--
Michael Horowitz
Your Computer Consultant_
__http://yourcomputerconsultant.com_ http://yourcomputerconsultant.com/
561-394-9079
***
List Guidelines: _http://webstandardsgroup.org/mail/guidelines.cfm_
Unsubscribe: _http://webstandardsgroup.org/join/unsubscribe.cfm_
Help: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
***
***
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]
***
***
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] multiple css style sheets
I think its also improper markup to have more than one stylesheet link so
@import might be a way to keep the code modular and still only have one
style sheet link.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Kane Tapping
Sent: Thursday, 28 February 2008 4:59 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] multiple css style sheets
Hi ,
I believe @import was originally used by designers to create styles Netscape
Navigator 4 would not implement incorrectly.
Some other reasons why you might use this rather then multiple link rel
declarations, include:
1. You can declare the @import within a CSS file style or style=
(you can also choose where in the CSS document to @import, allowing greater
control of the cascade's.)
2. link rel can only be declared in the head of a document (some
systems do not give access to this area, or only allow a set link to their
stylesheet.)
Kind Regards,
Kane Tapping
Web Standards Developer
Web and Content Management Services
Griffith University. 4111. Australia.
mailto://[EMAIL PROTECTED]/ [EMAIL PROTECTED]
Phone: +61 (0)7 3735 7630
Michael Horowitz [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
28/02/2008 01:46 PM
Please respond to
wsg@webstandardsgroup.org
To
wsg@webstandardsgroup.org
cc
Subject
Re: [WSG] multiple css style sheets
Is there a difference or specific reason to use the @import
Michael Horowitz
Your Computer Consultant
http://yourcomputerconsultant.com
561-394-9079
Kane Tapping wrote:
Hi ,
How do browsers determine the winner in a conflict... well, AFAIK,
they take the first style that is most relevant to the element.
That would be the LAST style that is most relevant to the element.
(unless !important is used to override the cascade.)
It also worth noting that multiple stylesheets are also commonly
referenced within CSS using @import.
The main benefit of using multiple stylesheets is for modular code.
Kind Regards,
Kane Tapping
Web Standards Developer
Web and Content Management Services
Griffith University. 4111. Australia._
[EMAIL PROTECTED] mailto://[EMAIL PROTECTED]/
Phone: +61 (0)7 3735 7630
*Steven Workman [EMAIL PROTECTED]*
Sent by: [EMAIL PROTECTED]
28/02/2008 03:36 AM
Please respond to
wsg@webstandardsgroup.org
To
wsg@webstandardsgroup.org
cc
Subject
Re: [WSG] multiple css style sheets
Michael,
Multiple style sheets are quite common in large sites. Splitting your
stylesheets into a basics, main and special cases is good for
keeping your code separate, also allowing multiple developers to work
on different areas of a site's styles without interrupting each other.
It's also becoming more common that any off the shelf javascript
techniques come with their own stylesheets i.e. Cody Lindley's Thickbox.
How do browsers determine the winner in a conflict... well, AFAIK,
they take the first style that is most relevant to the element.
Say you had ullispan class=bobSome text/span/li/ul
If your first stylesheet said:
ul li { color:red;
}
and the second one said
.bob { color: blue;
}
It would render as *blue*.
However, if the first one said
ul li .bob { color:red;
}
and the second one remained the same
.bob { color: blue;
}
It would render as *red
*
Steve Workman
PA Consulting Group_
__www.paconsulting.com_ http://www.paconsulting.com/_
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]_
__www.steel-software.com_ http://www.steel-software.com/
On 27/02/2008, *Michael Horowitz*
[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Just inherited a site and saw pages with multiple style sheets. Is
there a reason for that and how does the browser determine what to use
if there is a conflict
--
Michael Horowitz
Your Computer Consultant_
__http://yourcomputerconsultant.com_ http://yourcomputerconsultant.com/
561-394-9079
***
List Guidelines: _http://webstandardsgroup.org/mail/guidelines.cfm_
Unsubscribe: _http://webstandardsgroup.org/join/unsubscribe.cfm_
Help: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
***
***
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]
***
