On Sun, Feb 15, 2009 at 07:54:15PM +0100, Hofmann Johannes wrote:
On Sun, Feb 15, 2009 at 03:57:46PM -0300, Jorge Arellano Cid wrote:
On Sun, Feb 15, 2009 at 05:07:28PM +0000, corvid wrote:
Johannes wrote:
On Sat, Feb 14, 2009 at 04:07:15PM +0000, corvid wrote:
Johannes wrote:
On Sun, Feb 01, 2009 at 07:20:33PM +0000, corvid wrote: > I was just looking at some of the prefs that I > don't think are doing anything right now, e.g., > link_color, force_my_colors... > I could stuff them into buildUserStyle(), but > I don't know which should prevail in case of > conflicts. > > I can't remember whether I've already mentioned that > I've been wondering whether it might be reasonable to > rip a bunch of color stuff out of dillorc and expect > a dillo user to be able to deal with a well-commented > sample style.css instead.
Good point. I always favor simplicity so I think we should have just one way to modify the style. Having two (style.css and preferences) just adds confusion. We need to document this properly as you said.
If I have a style.css containing:
* {font-size: 30px}
and a page containing:
regular regular <span>large</span>
Can it be interpreted as "make everything big"?
Sorry, I think I don't fully understand the question.
* {font-size: 30px !important}
would set a fixed font size of 30px. The <span> itself doesn't alter it. What am I missing?
If I do this, it doesn't use 30px until the first tag it sees.
BTW, there's BUG#892 (prefs' bg_color is not working).
Jorge, what do you think about this? Can we go the style.css way and remove all dillorc options for stuff that can also be done with style.css?
I'm very happy with the latest patches on font size, it's very important: http://www.useit.com/alertbox/designmistakes.html Reading that page is assuring. We're providing the necessary controls for people expressing their need for them! WRT your question, yes, it'd be good to go the CSS way, but also to keep it simple for a non-CSS-savvy user to set. This is, maybe font_{min_size, max_size, factor} are well placed in dillorc. For text background and color, linkcolor, visited linkcolor they seem to belong in CSS. Now, if we're to put them in CSS, we must provide well-commented sample stylesheets, and also give some directions in the FAQ. It should be simple for the user to know how to set his own stylesheet options without previous CSS knowledge, and also how to disable the remote CSS when a page doesn't look good. It'd be great to specify, for instance, a "reading" stylesheet (for low contrast and highcontrast) from our website and to let the user tweak it. Then when he gets to a long page that he wants to read (not just skim), he could disable remote CSS and use the one he prefers. A few days ago I got to read the above link and relized the actual relevance of this issue. -- Cheers Jorge.-