You asked which of the proposed changes to the code I would like to see.

I was kidding about stealing your font, not kidding about what changes you want.

If we can easily set up cascade so that there's a barebones resulting style -- it seems a good thing for usability too, fug aside.

I like Verdana, but I don't want it to be the default for every site I visit. I'd be fine with making the b.org font selectable.

If we can easily set up cascade so that there's a barebones resulting style

Seems like that should be doable, but I'd need to experiment.

ita - did you get my email with the new bookmarks page?

I've got it, Jon, but I haven't had a chance to look at the HTML yet. My internet connection is going to be inconvenient until the weekend.

Seems like that should be doable, but I'd need to experiment.

From an automation PoV, do you think it will be best to have one base stylesheet and then a selectable one?

If we can get it to work, I'm thinking one base stylesheet, and then a style tag in every page's header with the font, either immediately before or after the base stylesheet (however that works, I can never remember).

I'm thinking one base stylesheet, and then a style tag in every page's header with the font, either immediately before or after the base stylesheet (however that works, I can never remember).

I'm thinking of a consistent mechanism to handle all the available styles, though. Can all the scenarios be handled the same way? Because I think we should prioritise the ones that can be abstracted and handled with a system.

I like systems.

Are you thinking customizable stylesheets, but limited to a set of choices? Or fully customizable? For example, fonts: Would we give folks a list of possible font sets to choose from, or could they type in whatever font they wanted?

If it's the latter, you may need user-specific stylesheets. If it's the former, then we could set up a stack of stylesheets for however many permutations we need. But that could get messy if we allow more than a few elements to be user-definable.

Actually, the more I think about it, if you want a system, then the easiest thing might be user-specific stylesheets.

Why not just a small set of alternate style sheets?

That's the scenario I'm thinking of, Tom. I'm just wondering how much we can keep in common (the base file), and then cascade another file on top of that. I get how you can change a previously defined style with a second sheet, but can you erase it?

It's a shame we didn't get the XSLT thing going. Maybe later.

We don't need to erase. There can be a second stylesheet that acts as the default for all the changeable stuff. If you want to have the ability to "erase" a style, leave it off of the main sheet, put it in the second default sheet, but exclude it from an alternate choosable second sheet.