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

Quoted attribute parsing: summary

by Johannes.Hofmann＠gmx.de

On Mon, Aug 16, 2010 at 07:21:02AM +0100, Jeremy Henty wrote: > > Prompted by some private conversation with corvid I've been digging > through specs and source code to see what the state of play is. > > The HTML5 specification[1] states that the user agent should consume > text, converting character references until it finds the matching > close quote. If there is no matching close quote (ie. it sees an EOF > first) then it terminates (strictly speaking, it switches to the data > state and reconsumes the EOF, which makes it emit an EOF token). > > Taking out Dillo's bogus attribute value detection as I proposed would > make Dillo parse quoted attribute values as per the HTML5 spec. > > The Hubbub HTML parser library[2] parses quoted attribute values as > per the HTML5 spec. > > Firefox parses quoted attribute values as per the HTML5 spec *except* > that if it sees an EOF then it backs up to the open quote, discards > it, then reparses as though it was expecting an unquoted attribute > value. Otherwise (ie. if it finds the matching close quote) it makes > no attempt to detect a broken attribute value, no matter what content > the attribute value has swallowed up. > > So it seems that the world at large has given up on trying to detect > and correct broken attribute values. I'd agree that we should not make compromises displaying correct HTML when trying to deal with buggy HTML. But are the '>' characters in the attribute value in the reddit page actually valid? The HTML validators at least warn about them. Cheers, Johannes

Aug. 16, 2010

Quoted attribute parsing: summary

by onepoint＠starurchin.org

Prompted by some private conversation with corvid I've been digging through specs and source code to see what the state of play is. The HTML5 specification[1] states that the user agent should consume text, converting character references until it finds the matching close quote. If there is no matching close quote (ie. it sees an EOF first) then it terminates (strictly speaking, it switches to the data state and reconsumes the EOF, which makes it emit an EOF token). Taking out Dillo's bogus attribute value detection as I proposed would make Dillo parse quoted attribute values as per the HTML5 spec. The Hubbub HTML parser library[2] parses quoted attribute values as per the HTML5 spec. Firefox parses quoted attribute values as per the HTML5 spec *except* that if it sees an EOF then it backs up to the open quote, discards it, then reparses as though it was expecting an unquoted attribute value. Otherwise (ie. if it finds the matching close quote) it makes no attempt to detect a broken attribute value, no matter what content the attribute value has swallowed up. So it seems that the world at large has given up on trying to detect and correct broken attribute values. Jeremy Henty [1] http://www.whatwg.org/specs/web-apps/current-work/multipage/ [2] http://www.netsurf-browser.org/projects/hubbub/

Aug. 16, 2010

Debian/Ubuntu packages available

by rogerx＠sdf.org

On Sun, Aug 08, 2010 at 06:54:25PM +0200, Devid Antonio Filoni wrote: >I sent an email time ago with that link, I don't know why dillo.org >was not updated. However there is also >https://edge.launchpad.net/~d.filoni/+archive/dillo+ssl/+packages No problem here... Gentoo is up to date. ;-) -- Roger http://rogerx.freeshell.org/

Aug. 9, 2010

Debian/Ubuntu packages available

by devidfil＠gmail.com

I sent an email time ago with that link, I don't know why dillo.org was not updated. However there is also https://edge.launchpad.net/~d.filoni/+archive/dillo+ssl/+packages Devid On Sun, Aug 8, 2010 at 10:12 AM, Alexander Voigt <Hole.destructor(a)gmx.de> wrote: > Dear Dillo developers and users, > > I found that Devid Antonio Filoni provides Debian/Ubuntu packages of > the current dillo release at > > ? https://launchpad.net/~d.filoni/+archive/dillo/+packages > > Maybe this is worth to mentioned at dillo.org. > > Kind regards, > Alexander Voigt > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

Aug. 8, 2010

Debian/Ubuntu packages available

by Hole.destructor＠gmx.de

Dear Dillo developers and users, I found that Devid Antonio Filoni provides Debian/Ubuntu packages of the current dillo release at https://launchpad.net/~d.filoni/+archive/dillo/+packages Maybe this is worth to mentioned at dillo.org. Kind regards, Alexander Voigt

Aug. 8, 2010

[patch]: do not let '>' terminate a quoted attribute value

by jcid＠dillo.org

On Sun, Aug 01, 2010 at 12:56:23PM +0100, Jeremy Henty wrote: > > If you point dillo at http://www.reddit.com/ you will see many > javascript fragments. These come from div elements with an > onclick="$(this).vote('<$>votehash</$>', null, event)" attribute. > Dillo thinks that the '>' looks suspiciously like an end tag > character. It looks ahead, sees the '<' character and decides that > its suspicions are correct, so it terminates the tag at the '>', warns > of a missing attribute close quote and renders the rest as HTML. > > This algorithm may have been effective in the early days of the web > but I think it clearly does not work well today. I can't think of a > better way of doing the job so I suggest removing it and instead just > finding the matching close quote in all cases. Patch attached. Effectively, this is a problem. Unfortunately the final-quote approach creates more trouble than it seems. See doc/HtmlParser.txt for an explanation. A simple heuristic that can tackle both cases equally well, would certainly be appreciated. For instance, if there's a missing quote (according to current heuristics), and there's an unmatched '(' in the atribute value, we may try to look for a matching ')' in the vicinity, and if found, look for the closing quote afterwards. If found, we can change the first decision. This approach has low testing cost (O(n) in case of missing quote), and may help discriminate both cases: real missing quote and scripting language. -- Cheers Jorge.-

Aug. 6, 2010

[Thank you very much.]

by jcid＠dillo.org

On Fri, Aug 06, 2010 at 11:14:55AM +0200, Johannes Hofmann wrote: > On Fri, Aug 06, 2010 at 11:00:05AM +0200, Johannes Hofmann wrote: > > Hi, > > > > > > > > I'm an Ubuntu user. My connection speed is just 5kbps. > > > Dillo is just amazing!! It opens the web pages in seconds. > > > > That's good to hear. > > > > > > > > When i right click on a web page, it automatically chooses previous > > > option. Thank you very much. > > > > Yeah, that's a nice feature of the fltk toolkit. It does this > > automatically. > > > > > > > > But I'm not be able to view 'TAMIL' language sites. Is there anyway to > > > view tamil sites? > > > > What exactly does not work? Are you seeing little square instead of > > tamil characters? > > In that case you can try to install FreeSans and FreeSerif, which > > are part of the freefont package. > > Then change the fonts in your dillorc to: > > > > font_sans_serif="FreeSerif" > > font_sans_serif="FreeSans" > > Argh, that should of course read: > > font_serif="FreeSerif" > font_sans_serif="FreeSans" Just forwarded a corrected version to the guy, and suggested a dillo-dev subscription if he wants to follow the thread. -- Cheers Jorge.-

Aug. 6, 2010

[Thank you very much.]

by Johannes.Hofmann＠gmx.de

On Fri, Aug 06, 2010 at 11:00:05AM +0200, Johannes Hofmann wrote: > Hi, > > > > > I'm an Ubuntu user. My connection speed is just 5kbps. > > Dillo is just amazing!! It opens the web pages in seconds. > > That's good to hear. > > > > > When i right click on a web page, it automatically chooses previous > > option. Thank you very much. > > Yeah, that's a nice feature of the fltk toolkit. It does this > automatically. > > > > > But I'm not be able to view 'TAMIL' language sites. Is there anyway to > > view tamil sites? > > What exactly does not work? Are you seeing little square instead of > tamil characters? > In that case you can try to install FreeSans and FreeSerif, which > are part of the freefont package. > Then change the fonts in your dillorc to: > > font_sans_serif="FreeSerif" > font_sans_serif="FreeSans" Argh, that should of course read: font_serif="FreeSerif" font_sans_serif="FreeSans" Cheers, Johannes

Aug. 6, 2010

[Thank you very much.]

by Johannes.Hofmann＠gmx.de

Hi, > > I'm an Ubuntu user. My connection speed is just 5kbps. > Dillo is just amazing!! It opens the web pages in seconds. That's good to hear. > > When i right click on a web page, it automatically chooses previous > option. Thank you very much. Yeah, that's a nice feature of the fltk toolkit. It does this automatically. > > But I'm not be able to view 'TAMIL' language sites. Is there anyway to > view tamil sites? What exactly does not work? Are you seeing little square instead of tamil characters? In that case you can try to install FreeSans and FreeSerif, which are part of the freefont package. Then change the fonts in your dillorc to: font_sans_serif="FreeSerif" font_sans_serif="FreeSans" Note however, that you might also need to force the use of these new default fonts in case the webpage chooses a different font explicitely. To do that add e.g. * {font-family: sans-serif !important} to your ~/.dillo/style.css file. Hope that helps, Johannes

Aug. 6, 2010

[sethupathy3e@gmail.com: Thank you very much.]

by jcid＠dillo.org

-- Cheers Jorge.-

Aug. 5, 2010