Hi there! I just commited the new (big) patch that adds a "bug meter" to Dillo's UI. From the Changelog: + Added a bug-meter button that shows the count of detected HTML errors (left click shows the errors, right click offers a validation menu). + Removed the "show_html_warnings" option from dillorc. + Cleaned up the code for the progressbar widgets. Most probably this CVS, plus a few improvements to our configure stuff (compiling in old distros, png detection and proper library linking) will be the basis for dillo-0.8.0-rc1. Please test it and enjoy! Cheers Jorge.- PS: I'm for letting "combat mode" rendering and https for 0.8.1 as its been too much time without a release.
On Sun, 25 Jan 2004, Jorge Arellano Cid wrote:
I just commited the new (big) patch that adds a "bug meter" to Dillo's UI. From the Changelog:
+ Added a bug-meter button that shows the count of detected HTML errors (left click shows the errors, right click offers a validation menu). + Removed the "show_html_warnings" option from dillorc. + Cleaned up the code for the progressbar widgets.
Very snazzy. Slashdot shows 14. Then I look I my work home page (<http://www.jlab.org/~dmckee/>) which I know is buggy because the computer center prepends a bit of junk to each file at the time it is served. I get seven errors and the details are: | +---------- HTML warning: line 5, color is not in "#RRGGBB" format HTML warning: line 15, HEAD element must go before the BODY section HTML warning: line 16, META elements must be inside the HEAD section HTML warning: line 17, META elements must be inside the HEAD section HTML warning: line 18, META elements must be inside the HEAD section HTML warning: line 19, META elements must be inside the HEAD section HTML warning: line 20, the TITLE element must be inside the HEAD section +---------- | The first one belongs to the code the CC puts in. The rest come from my (correctly formed) header: having decided that I must already be in the body, dillo gets upset when it sees header stuff... I don't know that this is worth worring about---the real problem is that the CC is knowingly serving broken code because sending good code would mean parsing each page to find the top of <body> as it is being served. Not really dillo's problem, but I thought I'd mention it.
Most probably this CVS, plus a few improvements to our configure stuff (compiling in old distros, png detection and proper library linking) will be the basis for dillo-0.8.0-rc1.
Sounds good.
PS: I'm for letting "combat mode" rendering and https for 0.8.1 as its been too much time without a release.
Sure. The CVS has been fairly bug free and _much_ better that 0.7.3 for some time. Get a new release out, and if the rest of that stuff comes together quickly, well you just get to have a fast release schedule. -- -- David McKee -- dmckee@jlab.org -- (757) 269-7492 (Office)
In article <Pine.LNX.4.58.0401251925460.10896@infinity.cl>, Jorge Arellano Cid <jcid@dillo.org> writes
Most probably this CVS, plus a few improvements to our configure stuff (compiling in old distros, png detection and proper library linking) will be the basis for dillo-0.8.0-rc1.
Good news! Probably won't get round to testing for a few days, so an early warning on a more worrying recent bug... - my experience of recent cvs, compiled on the playstion2, (blackrhino 2.2.21 kernel), apparently shows a disconcerting feature. After a few minutes of scrolling up and down standard web-sites the whole system will hang (eg it's unpingable, and doesn't respond to any keyboard input), and needs a hard reset :-( Anyone else currently testing on the ps2 please (and hopefully had better experiences, or a fix)?? Bob -- robert w hall
participants (3)
-
David McKee -
Jorge Arellano Cid -
robert w hall