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? Cheers, Johannes