S2 Styles Should Always Allow Browser Defaults
Short, concise description of the idea
Allow "use browser default" as an option for certain common style customizations, and use that as a default as appropriate
Full description of the idea
Currently, many of the S2 styles specify colors for links, text, and background colors, and fonts, in their stylesheets. The defaults are taken from the defaults of the style. There doesn't appear any way to have the style refrain from specifying these things, and letting the browser take over from whatever defaults the user has selected in their browser.
Whether or not a style users "use browser default" as its defaults for particular customzations is up to the style designer, although I prefer that this be the case.
An ordered list of benefits
Principle of least surprise: user gets the same fonts and link colors (and hover behavior) that they see on other pages.
Not messing with these parameters respects accessibility for vision-impaired users.
An ordered list of problems/issues involved
Might require tweaks to S2 itself (I don't know enough about it). It is realy a simple matter of refraining from generating style attributes to go into the stylesheet.
Standard S2 styles would be to be evaluated and updated to show how it's done.
Some color schemes would not work well with typical link or text colors that are usual chosen at defaults in browsers.
An organized list, or a few short paragraphs detailing suggestions for implementation
If "use browser default" is the option, refrain from generating a stylesheet attribute directive so that the brower can take over.
When a style offers themes for combinations of colors, one theme could be associated with "browser default," refraining from specifying most style attributes, and using neutral or common choices for those design elements which can't be taken from browser defaults.