Hi, On Fri, Jul 24, 2009 at 11:33:28AM -0400, Jorge Arellano Cid wrote:
Hi,
Here are some pending issues which I've partially sorted by priority (at least the top half). Please add the missing ones and let's try to finish sorting it, with a view to planify our work.
* Make DIV-based pages render correctly. This is the most visible rendering fault in Dillo. The textblock doesn't have a way to handle it (not implemented). IIRC I'm willing to dig into it and Johannes will help. e.g. http://www.advogato.org/faq.html
With DIV-based pages you mean floats as in http://www.w3.org/TR/CSS21/visuren.html#floats? Yes, this is the most obvious rendering problem atm.
* Add blocker (this also has to do with privacy). A full RE-based one may have significant overhead (test required), but simple string-matching may do most of the trick. I've also thought for a long time that a "don't load from other sites" preference may help a lot. The whole topic needs some thought but it's not hard to implement. e.g. doubleclick.
* Handle negative values in CSS. e.g. wikipedia.
Actually it's dw/* that needs to be adapted to handle negative margins. This might be related to the floats stuff.
* What will we do with xhtml? To render or not to render... FF doesn't validate. BUG#732 One solution is to add a notification widget area below the control panel that hides/unhides as the find bar, to warn when a xhtml file has detected bugs (we'd also move the meta refresh warning to display here). I already have a simple patch to add xhtml rendering. The widget implemetation is the missing part. It should be much simpler than the close button in each tab. :-) e.g. http://planet.postgresql.org/
* Jump to #anchor doesn't work correctly. It looks like a timing issue, but the idle-call API needs a review as a whole.
* dpi for "view page source" (it re-uses search capability). This requires a check of the current data-passing inside DPIP.
* Improve the DPI development/debug framework.
* https dialog bombing issue. BUG#868 AKA make https dpi a server (i.e. not a filter dpi).
* Render bug at http://www.directfb.org/ (and its links). The table has too wide a first column. Back/Fwd solves it.
Yes, I've seen this on several pages.
* handling in fltk.org The relevant point is to define a consistent way to handle whitespace in the textblock.
Can you explain the problem a bit?
* FTP download doesn't work?!
wget - based downloads work mostly fine for me. Where do you see an issue? I've got one more point: * Add clipping to the fltk drawing code, so that e.g. margins of huge boxes don't cause X11 coordinate overflows. E.g. on http://alpen-panoramen.de/newcomments.php I will try to fix that. Similar issues occur with very long lines in plain.cc. Cheers, Johannes