I was trying the new search functionality a bit more
and found this (it's also present in my Dec 2008 dillo*).
With the page:
<table>
<tr><td>no close-tr
<tr><td>has a close-tr</tr>
<tr><td>here's another line</tr>
</table>
if I search for "rh", it finds one instance of it
split between the second and third table rows.
* My older dillos were lost in a tragic "I don't think I
need my CVS stuff anymore" accident.
Hi,
this http://wtikay.com/docs/details.html is quite interesting. Dillo
is not vulnerable, but we should keep this in mind when implementing
background image support.
Cheers,
Johannes
corvid, you have just fixed an issue with horizontal scrolling
during search.
While testing it I realized, that horizontal scrolling during search
does not work at all with plain text. Any idea why?
Cheers,
Johannes
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
* 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.
* 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.
* handling in fltk.org
The relevant point is to define a consistent way to handle
whitespace in the textblock.
* FTP download doesn't work?!
--
Cheers
Jorge.-
