I get the feeling we are close to releasing dillo-2.1. Do others agree? What's left to be done? Regards, Jeremy Henty
On Sat, Jan 31, 2009 at 01:15:07PM +0000, Jeremy Henty wrote:
I get the feeling we are close to releasing dillo-2.1. Do others agree? What's left to be done?
I agree. Of course there is a lot todo regarding CSS conformance, but we won't pass any ACID test soon anyway. I'd like to get the font-size issue on wikipedia.org fixed however - help on that is very welcome :-). Regards, Johannes
On Sat, Jan 31, 2009 at 03:08:20PM +0100, Hofmann Johannes wrote:
On Sat, Jan 31, 2009 at 01:15:07PM +0000, Jeremy Henty wrote:
I get the feeling we are close to releasing dillo-2.1. Do others agree? What's left to be done?
I agree. Of course there is a lot todo regarding CSS conformance, but we won't pass any ACID test soon anyway. I'd like to get the font-size issue on wikipedia.org fixed however - help on that is very welcome :-).
and there's the "minimal_font_size" pref. I may look into this after dicache... -- Cheers Jorge.- ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
On Sat, Jan 31, 2009 at 03:08:20PM +0100, Hofmann Johannes wrote:
On Sat, Jan 31, 2009 at 01:15:07PM +0000, Jeremy Henty wrote:
I get the feeling we are close to releasing dillo-2.1. Do others agree? What's left to be done?
I agree. Of course there is a lot todo regarding CSS conformance, but we won't pass any ACID test soon anyway. I'd like to get the font-size issue on wikipedia.org fixed however - help on that is very welcome :-).
Ah!, and there's the very important issue of the visited link color. When coming back to a page, most of the time visited links aren't shown as such (i.e. drawn in visited color). -- Cheers Jorge.- ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
On Sat, Jan 31, 2009 at 12:04:32PM -0300, Jorge Arellano Cid wrote:
On Sat, Jan 31, 2009 at 03:08:20PM +0100, Hofmann Johannes wrote:
On Sat, Jan 31, 2009 at 01:15:07PM +0000, Jeremy Henty wrote:
I get the feeling we are close to releasing dillo-2.1. Do others agree? What's left to be done?
I agree. Of course there is a lot todo regarding CSS conformance, but we won't pass any ACID test soon anyway. I'd like to get the font-size issue on wikipedia.org fixed however - help on that is very welcome :-).
Ah!, and there's the very important issue of the visited link color. When coming back to a page, most of the time visited links aren't shown as such (i.e. drawn in visited color).
Do you have an example? CSS allows to specify the visited link color, so it may just have been set by the author to something unexpected. Does :visited {color: #800080 !important} in .dillo/style.css fix the problem? Cheers, Johannes
On Sat, Jan 31, 2009 at 04:03:11PM +0100, Hofmann Johannes wrote:
On Sat, Jan 31, 2009 at 12:04:32PM -0300, Jorge Arellano Cid wrote:
On Sat, Jan 31, 2009 at 03:08:20PM +0100, Hofmann Johannes wrote:
On Sat, Jan 31, 2009 at 01:15:07PM +0000, Jeremy Henty wrote:
I get the feeling we are close to releasing dillo-2.1. Do others agree? What's left to be done?
I agree. Of course there is a lot todo regarding CSS conformance, but we won't pass any ACID test soon anyway. I'd like to get the font-size issue on wikipedia.org fixed however - help on that is very welcome :-).
Ah!, and there's the very important issue of the visited link color. When coming back to a page, most of the time visited links aren't shown as such (i.e. drawn in visited color).
Do you have an example? CSS allows to specify the visited link color, so it may just have been set by the author to something unexpected.
http://www.linux.org.uk/Portaloo.cs (but as you said, this one sets to the same color). http://www.lacuarta.cl If you click on a red headline and come back, the color is the same. I don't know what color is visited set to.
Does
:visited {color: #800080 !important}
in .dillo/style.css fix the problem?
Yes. It always shows the same visited-color, but is much better than without. Personally, I like best something like the old "contrast visited color" ;) -- Cheers Jorge.- ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
On Sat, Jan 31, 2009 at 02:38:47PM -0300, Jorge Arellano Cid wrote:
On Sat, Jan 31, 2009 at 04:03:11PM +0100, Hofmann Johannes wrote:
On Sat, Jan 31, 2009 at 12:04:32PM -0300, Jorge Arellano Cid wrote:
On Sat, Jan 31, 2009 at 03:08:20PM +0100, Hofmann Johannes wrote:
On Sat, Jan 31, 2009 at 01:15:07PM +0000, Jeremy Henty wrote:
I get the feeling we are close to releasing dillo-2.1. Do others agree? What's left to be done?
I agree. Of course there is a lot todo regarding CSS conformance, but we won't pass any ACID test soon anyway. I'd like to get the font-size issue on wikipedia.org fixed however - help on that is very welcome :-).
Ah!, and there's the very important issue of the visited link color. When coming back to a page, most of the time visited links aren't shown as such (i.e. drawn in visited color).
Do you have an example? CSS allows to specify the visited link color, so it may just have been set by the author to something unexpected.
http://www.linux.org.uk/Portaloo.cs
(but as you said, this one sets to the same color).
If you click on a red headline and come back, the color is the same. I don't know what color is visited set to.
Yes, that's expected. They set the color for visited links. firefox also shows them in red.
Does
:visited {color: #800080 !important}
in .dillo/style.css fix the problem?
Yes.
It always shows the same visited-color, but is much better than without. Personally, I like best something like the old "contrast visited color" ;)
That's problematic. I don't know how to express this in CSS and hacking this around CSS seems ugly. Maybe adding some special dillo specific CSS extension would be possible. But before doing that we should make sure that it really can't be done with standard CSS. Also we should check what other browsers do. Cheers, Johannes
On Sat, Jan 31, 2009 at 06:53:47PM +0100, Hofmann Johannes wrote:
On Sat, Jan 31, 2009 at 02:38:47PM -0300, Jorge Arellano Cid wrote:
On Sat, Jan 31, 2009 at 04:03:11PM +0100, Hofmann Johannes wrote:
On Sat, Jan 31, 2009 at 12:04:32PM -0300, Jorge Arellano Cid wrote:
On Sat, Jan 31, 2009 at 03:08:20PM +0100, Hofmann Johannes wrote:
On Sat, Jan 31, 2009 at 01:15:07PM +0000, Jeremy Henty wrote:
I get the feeling we are close to releasing dillo-2.1. Do others agree? What's left to be done?
I agree. Of course there is a lot todo regarding CSS conformance, but we won't pass any ACID test soon anyway. I'd like to get the font-size issue on wikipedia.org fixed however - help on that is very welcome :-).
Ah!, and there's the very important issue of the visited link color. When coming back to a page, most of the time visited links aren't shown as such (i.e. drawn in visited color).
Do you have an example? CSS allows to specify the visited link color, so it may just have been set by the author to something unexpected.
http://www.linux.org.uk/Portaloo.cs
(but as you said, this one sets to the same color).
If you click on a red headline and come back, the color is the same. I don't know what color is visited set to.
Yes, that's expected. They set the color for visited links. firefox also shows them in red.
Does
:visited {color: #800080 !important}
in .dillo/style.css fix the problem?
Yes.
It always shows the same visited-color, but is much better than without. Personally, I like best something like the old "contrast visited color" ;)
That's problematic. I don't know how to express this in CSS and hacking this around CSS seems ugly. Maybe adding some special dillo specific CSS extension would be possible. But before doing that we should make sure that it really can't be done with standard CSS. Also we should check what other browsers do.
Yes. In its current state: :visited {color: #800080 !important} is enough for a release. Maybe in the future we can modify the custom dillo stylesheet with a computed visited color, on-the-fly for each page. Is that possible? -- Cheers Jorge.- ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
Johannes wrote:
On Sat, Jan 31, 2009 at 01:15:07PM +0000, Jeremy Henty wrote:
I get the feeling we are close to releasing dillo-2.1. Do others agree? What's left to be done?
I agree. Of course there is a lot todo regarding CSS conformance, but we won't pass any ACID test soon anyway. I'd like to get the font-size issue on wikipedia.org fixed however - help on that is very welcome :-).
That reminds me, it would be good to add some checking for malicious values before release.
On Sun, Feb 01, 2009 at 05:57:59PM +0000, corvid wrote:
Johannes wrote:
On Sat, Jan 31, 2009 at 01:15:07PM +0000, Jeremy Henty wrote:
I get the feeling we are close to releasing dillo-2.1. Do others agree? What's left to be done?
I agree. Of course there is a lot todo regarding CSS conformance, but we won't pass any ACID test soon anyway. I'd like to get the font-size issue on wikipedia.org fixed however - help on that is very welcome :-).
That reminds me, it would be good to add some checking for malicious values before release.
Yes, I think stylengine.cc would be the right place. Maybe we can add some generic checks and remove the ones in html.cc - this needs to be checked. We also need to give cssparser.cc a thorough look regarding potential buffer overflows... Cheers, Johannes
On Sun, Feb 01, 2009 at 07:20:58PM +0100, Hofmann Johannes wrote:
On Sun, Feb 01, 2009 at 05:57:59PM +0000, corvid wrote:
Johannes wrote:
On Sat, Jan 31, 2009 at 01:15:07PM +0000, Jeremy Henty wrote:
I get the feeling we are close to releasing dillo-2.1. Do others agree? What's left to be done?
I agree. Of course there is a lot todo regarding CSS conformance, but we won't pass any ACID test soon anyway. I'd like to get the font-size issue on wikipedia.org fixed however - help on that is very welcome :-).
That reminds me, it would be good to add some checking for malicious values before release.
Yes, I think stylengine.cc would be the right place. Maybe we can add some generic checks and remove the ones in html.cc - this needs to be checked. We also need to give cssparser.cc a thorough look regarding potential buffer overflows...
At some point in time the whole browser will need a check against malicious/random data. The dillo-2.x process has been focused on features. I agree that the CSS part needs a review before release. -- Cheers Jorge.- ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
On Sat, Jan 31, 2009 at 01:15:07PM +0000, Jeremy Henty wrote:
I get the feeling we are close to releasing dillo-2.1. Do others agree? What's left to be done?
It looks like the main part is done. The close-tab icon is still missing (Jo?o Ricardo is working on it). I'm yet to push more dicache/image cleanups and to update the respective docs. There're more valgrind issues to look into. It would also be interesting to look at the addblock code; corvid made a prototype based on RE. I have the feeling (i.e. not backed with actual data) that maybe an option to not load resources from sites other than where the page is hosted, would get rid of most of the problems cheaply. Another posibility is to filter by host (dStrncasecmp() against URL_HOST), and maybe also offer RE filtering for more fine tunning (comments encouraged). CSS, we need Johannes green light on this. More stabilizing & testing. After that, custom packages need to be built for Debian, Ubuntu, RedHat... We may be more or less one month away... -- Cheers Jorge.- ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
participants (4)
-
corvid＠lavabit.com -
jcid＠dillo.org -
Johannes.Hofmann＠gmx.de -
onepoint＠starurchin.org