On Thu, Jan 15, 2009 at 10:41:59AM -0300, Jorge Arellano Cid wrote:

Hi Johannes,

On Thu, Jan 15, 2009 at 10:07:37AM +0100, Hofmann Johannes wrote:

...

Hi Jorge,

On Wed, Jan 14, 2009 at 07:07:00PM -0300, Jorge Arellano Cid wrote:

...

Hi Johannes,

Here go couple of patches. Please test and apply.

Thanks, applied.

...

Note: the image background support is partial. It works well when coming back to a page. AFAIS the right solution is to decode transparent images to RGBA and let FLTK handle it.

Yes, I think that would be the correct way to do it.

...

BTW, the CSS prototype seems stable enough to consider a merge. What do you think?

Yes, it feels pretty stable and now that there is an option to disable remote stylesheet loading, I think we can consider making css-prototype the main branch of dillo. However I'd like to have some issues fixed:

* should load_stylesheets=NO only disable remote style-sheet loading (as it does now), or should it disable all remote style processing (e.g. style given in <style type="text/css"> </style>)?

We can add a "parse_embedded_css" option. That way there's no ambiguity.

My next task is to add the toolbox button mentioned in:

http://lists.auriga.wearlab.de/pipermail/dillo-dev/2008-December/005531.html

It may hold CSS options akin to:

[Tb Icon] .-------------------. .---------. | Change charset >|--------------------------------->| UTF-8 | | CSS >|-->.---------------. | Cp 1250 | | Free memory >|-. |* remote CSS | | ... | '-------------------' | |* embedded CSS | '---------' | |* use my CSS | | |* no CSS at all| | '---------------' | .------------------. '->| Images | | Local Files | | Everything unused | '-------------------'

Note: '*' means a toggle option Note2: "use my CSS" replaces "Force my colors"

We can polish from there.

Ok, but I think we can reduce the CSS part to * remote CSS - meaning separate stylesheets * embedded CSS - meaning CSS in <style></style> or style="" attribute I think we should always use "my CSS" if it exists. "no CSS at all" would be the same as no .dillo/style.css and "remote CSS" and "embedded CSS" switched off.

...

* form.cc is not yet converted to the new style handling and widget coloring is broken.

OK.

...

* css-prototype displays e.g. table borders in the current color not in shaded background-color as dillo-main does. This is because CSS 2.1 states: "If an element's border color is not specified with a border property, user agents must use the value of the element's 'color' property as the computed value for the border color. " (http://www.w3.org/TR/CSS21/box.html#border-color-properties) firefox however also uses a shaded background color. I'd don't know how to deal with that at the moment.

I'd say leave it as the standard says until it becomes an issue. In that case we can follow FF or decide better.

The problem is that I'm not sure I understand the standard properly. Firefox is generally pretty standard compliant. But it's not a big issue anyway.

...

Then there is of course tons of issues with CSS, but we can improve on that gradually.

That's the idea.

BTW, I have a question. How can a minimal font size be specified? Currently I have:

body {font-size: 18px !important}

The problem is that this can be overridden e.g. by later <font size=10> elements. * {font-size: 18px !important} should fix the font size to 18px. However we probabely want an non-CSS option in dillorc to set a minimum font size.

in style.css, but often pages come with smaller fonts. e.g. http://www.linux.org.uk/Portaloo.cs

For me is important because I have a problems reading tiny fonts, and my working laptop has a high screen resolution.

css-prototype seems to use pretty small fonts generally. This may be a bug. Cheers, Johannes