Re: [css-d] Creating your own stylesheet for a website
On May 3, 2009, at 3:44 AM, david wrote: I go to a website fairly regularly and their styles are horrible. It's just too painful for me to look at anymore. Is there away for me to create a Stylesheet for it and have my browser automatically override there styles? I know to many of you this might sound horrible but don't worry no designers feelings will get hurt... I'm sure that no designers were used in making the site. I go to lots of those. No time to create a user style sheet for each. My fast and dirty method makes the hideous and grotesque instantly readable, functional, and usable: Opera browserviewstyleuser mode. Firefox with Web Developer Toolbar: Ctrl-Shift-L turns off all stylesheets. Firefox without any add-on: View menu Page Style No style. Safari also has such an option. Turn on the debug menu, the option is: Develop menu disable styles This is an interesting experiment: http://lab.arc90.com/2009/03/readability.php Because face it, for the average user, user stylesheet are hard, very hard. To keep the whole thing relatively on topic: 1. the ability to disable page styling is interesting to analyse how muchyour page is structurally sound (does the page depends on page styling/css to make sense ?). 2. Question: how much do you think about the possibility of userstyles interfering with your stylesheets when you develop a site ? Philippe --- Philippe Wittenbergh http://l-c-n.com/ __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] css or javascript hacks for firefox
On May 2, 2009, at 8:16 PM, Gunlaug Sørtun wrote:
This reduced hack should otherwise work, at least back to Fx 1.5 (not
thoroughly tested)...
@-moz-document url-prefix() {
:rootbody ELEMENT-SELECTOR {/* fix old Gecko */}
:rootbody:not(:nth-child(0)):only-of-type*|*:not(|*)
ELEMENT-SELECTOR {/* correct value for new Gecko */}
}
You don't really need to make it that complicated
@-moz-document url-prefix() {
:rootbody ELEMENT-SELECTOR {/* fix Gecko 1.9.0 and older */}
:rootbody:only-of-type ELEMENT-SELECTOR {/* correct value for Gecko
1.9.1 + */}
}
works just as well :-)
Gecko 1.9.0 and older (Fx 3.0.x and older) don't understand the ':only-
of-type' pseudo-class. The second line just makes the selector a tad
more specific.
(not that I really recommend using this kind of stuff for all the
reasons you mentioned. And I wouldn't build the form as in the given
problem file).
Philippe
---
Philippe Wittenbergh
http://l-c-n.com/
__
css-discuss [cs...@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] css or javascript hacks for firefox
thank you all for the reply
thehttp://test3.dekkers.net/login.htm is the problem
what i don't understand is why not use the fix?
and if not, what is the correct way to build the HTML ?
thanks again
Ido
On Sun, May 3, 2009 at 4:09 AM, Philippe Wittenbergh e...@l-c-n.com wrote:
On May 2, 2009, at 8:16 PM, Gunlaug Sørtun wrote:
This reduced hack should otherwise work, at least back to Fx 1.5 (not
thoroughly tested)...
@-moz-document url-prefix() {
:rootbody ELEMENT-SELECTOR {/* fix old Gecko */}
:rootbody:not(:nth-child(0)):only-of-type*|*:not(|*)
ELEMENT-SELECTOR {/* correct value for new Gecko */}
}
You don't really need to make it that complicated
@-moz-document url-prefix() {
:rootbody ELEMENT-SELECTOR {/* fix Gecko 1.9.0 and older */}
:rootbody:only-of-type ELEMENT-SELECTOR {/* correct value for Gecko
1.9.1 + */}
}
works just as well :-)
Gecko 1.9.0 and older (Fx 3.0.x and older) don't understand the ':only-
of-type' pseudo-class. The second line just makes the selector a tad
more specific.
(not that I really recommend using this kind of stuff for all the
reasons you mentioned. And I wouldn't build the form as in the given
problem file).
Philippe
---
Philippe Wittenbergh
http://l-c-n.com/
__
css-discuss [cs...@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
__
css-discuss [cs...@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] css or javascript hacks for firefox
Ido dekkers wrote: thehttp://test3.dekkers.net/login.htm is the problem what i don't understand is why not use the fix? I see no problem with the fix in your case, because of the way it is built up and used. The simplified selector for Gecko 1.9.1 + suggested by Philippe, will actually make it even safer against future problems by utilizing progressive enhancement with (only) a selector that is unlikely to be removed from or changed in CSS standards and/or browser support. Generally: it is the unstable nature of new browser versions - especially beta versions of course, that makes us hesitate to add hacks that targets them. Only stable browser versions should be hacked at all, and then only when there's no other, sensible, option. Your markup - source order - is correct as is, and should rather not be modified in order to work around a CSS weakness (bug) in a browser. When compensating for browser bugs it is almost always better to rework or add something to the stylesheet, than to modify the markup. Years back we had no choice but to go through and modify both markup and stylesheets when we encountered especially problematic bugs, but these days sensible markup should be left as is and all hacks (if any are needed) should be kept in the stylesheets. Only IE6 still creates a few exceptions to this rule. regards Georg -- http://www.gunlaug.no __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] trying to learn to make css menu
Scott Brasted wrote: I am trying to learn to make menus using only css. I have always used javascript menus in the past, but I have been recently become convinced that there are enough people who, for whatever reason, do not have js enabled and will not see my truly fabulous menus. mega trim There are a good number of unobtrusive js menus around. Other than that you'll have to wait for a pro to answer your CSS questions, as I dunno and have no clue what you are talking about. As far as a real world example of replacing a js menu with a CSS menu, your post from 25 April 2009 http://archivist.incutio.com/viewlist/css-discuss/106103?highlight=Scott+Brasted might look like this [1] with the js menu replaced with a very simple CSS menu. [1] http://chelseacreekstudio.com/ca/garden/ __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
