August 2016 - Dillo-dev - lists.mailman3.com

Get Dillo to honour target=_blank
by nick＠linicks.net Aug. 29, 2016

Aug. 29, 2016

Hi all, How easy (or hard) would it be to get Dillo to honour the URL/FORM directive 'target="_blank" to get URL/CGI data returned in a new tab? I ahve looked at the code, seeing as Dillo already has tabs, but I just don't get C++ classes and stuff, and wouldn't know where to begin. The reason for asking this is if one has a form with a lot of data that needs processing, once submitted the data gets returned to the parent page... if there is a mistake, then you need to go back to the form, and as Dillo doesn't keep the previous page data, you have to fill it all in again. By diverting the output to a new tab, the previous parent window remains the same, ready for editing and processing again. Thanks, Nick -- Gosh that takes me back... or is it forward? That's the trouble with time travel, you never can tell." -- Doctor Who "Androids of Tara"

3 6

Underscores not drawn in pre with background color
by Hole.destructor＠gmx.de Aug. 17, 2016

Aug. 17, 2016

Hi Dillo developers, I stumbled upon a page with a lot of code snippets wrapped in a <pre> block, where Dillo seems to have a rendering problem: Underscores `_' are not drawn. I stripped down this real-world-example to the attached minimal html file which reproduces the problem: The page should render as follows: ============================================ softpoint_with_block() { { echo ""; } | ./softpoint.x leshouches } ============================================ However, in the development version of Dillo it renders as follows: ============================================ softpoint with block() { { echo ""; } | ./softpoint.x leshouches } ============================================ As you can see, the underscores in the function softpoint_with_block() are not drawn in Dillo. However, the underscores are drawn correcty if you * remove the style="..." specification from the <pre> block or * remove the line { echo ""; } | ./softpoint.x leshouches from the <pre> block content. Best regards, Alex

4 14

Underscores not drawn in pre with background color
by michael.baeuerle＠stz-e.de Aug. 15, 2016

Aug. 15, 2016

Nick Warne wrote: > On Sat, 23 Jul 2016 11:25:18 +0100 Nick Warne <nick at linicks.net> wrote: > > On Sat, 23 Jul 2016 11:13:19 +0100 Nick Warne <nick at linicks.net> wrote: > > > On Sat, 23 Jul 2016 10:01:59 +0100 Nick Warne <nick at linicks.net> wrote: > > > > On Fri, 22 Jul 2016 20:12:59 +0300 John Found <johnfound at asm32.info> wrote: > > > > > > > > > > Confirmed. I am using "Liberation Mono", but with "DejaVu Sans > > > > > Mono" have the same problem. It is probably because of the > > > > > characters height - the next row of text overwrites the > > > > > previous. The question is whether this is because of Dillo or > > > > > because of FLTK. > > > > > > > > > > The same font, used in Firefox renders correctly. > > > > > > > > This looks like a bug in the font: > > > > > > > > http://dejavu-fonts.org/wiki/Bugs/Archived > > > > > > > > (you need to scroll down a bit). > > > > > > > > I have version 2.34 installed - will see if I can reproduce it > > > > later. > > > > > > OK, I get the same issue. But if you change the font size, thus: > > > > > > <pre style="background-color: white; > > > font-size:105%;">softpoint_with_block() { > > > > > > the underscores are visible. > > > > Huh! Strangely the underscores become visible with font size set to > > 95% too! Only 100% renders them invisible? > > OK, turning off 'use embedded CSS' makes them visible too. > > CSS parsing error? Please check whether the problem is related to this FLTK STR I created some days ago: <http://www.fltk.org/str.php?L3321>

2 1

Good news in dillo's rendering!
by jcid＠dillo.org Aug. 4, 2016

Aug. 4, 2016

Hi there, Here go some good news. Originally I was to send this internally to the core devs, but as we've benefitted from the feedback of active users in the list, and their experiences with the patches (before/afterwards), on the sites they usually browse, it looks like a good idea to do it again. Since June 6, when this thread [1] was started by Sebastian, I've been investigating/working in problems related to it. This led to some extensive rendering tests that catched a laundry list of problems with our current tip (#4643 today). This is a list with brief explanations, taken from the testing data tables I've gathered so far: Problems: 1: overwrites text with images. 2: crops images (aspect ratio). 3: different layout. 4: overwrites text with text float. 5: overwrites text with text. 6: CPU HOG with: tmp.num.html, tmp.num.small.html 7: Missing page sections (sometimes works for the same page). 8: Small images cut in two sometimes ("ESP", "CRO", ...) 9: Wrong aspect ratio for images (text line height) 10: Page drawn with offset (but browser thinks other section is on screen). There're test cases for each one, and most of them were taken and reduced from real pages. Having reduced test cases is good, reduced and isolated tests is better, but the good news is that I have a couple of patches that solve all of them! I'm not saying dillo will be error-free hereafter, but that the root of a whole family of problems has been found and fixed, and this will make future testing much simpler. GROWS2 is the "Grand Redesign Of Widget Sizes" v2 by Sebastian. This is a very powerful and flexible concept whose design allows floats, layers (and absolutes in the future, and more). It has proven very fast so far, even without optimizations. Well the patches are two simple but deep changes in the way markSizeChange() and queueResize() interact. The patch idea is close to graph coverage recursions (with pruning), applied to the widget tree. I'd like to commit it, upload the test suite I'm using, and show the testing data tables I've gathered so everyone can check it with their use cases and report on it. @Sebastian: May I, or would you prefer to review them before? (the patches are the "middle ground" you mentioned. Solve the dw hog problems at dw level, not in the parser, and reuse code you've already seen. A couple of days should be enough to review) @Sebastian: Problem #10 is not related to GROWS2, but a three year old bug discovered during the tests. So let's get it done first. How to reproduce it: Go to [2], wait a bit for most images to load, then use "find text" to find the "re-re" string, scroll a bit downwards to find the image and center it. Go back then forward; no image! But dillo thinks it *is* there so move the cursor to the center of the page and you'll see the hand cursor, wait for the tooltip and drag it a bit downwards to the right. Dillo will repaint from the image data. Bisect shows the bug was introduced by #2863. Attached is a simple concept patch for it. Please review/fix/commit, as I don't know the updated invariants of resize idle. [1] http://lists.dillo.org/pipermail/dillo-dev/2016-June/010887.html [2] http://tinyurl.com/huvf6pn -- Cheers Jorge.-

2 4

Successful build on OS X
by gears_of_war__＠hotmail.com Aug. 4, 2016

Aug. 4, 2016

Dillo builds an runs on mac os x 10.5.8 (ppc32) with fltk-1.3.3. It runs great!

1 0