- Dillo-dev - lists.mailman3.com

fltk release

by corvid＠lavabit.com

I was thinking of making README and the website not so 1.3.0-specific now that 1.3.1 is out, but it would be nice to get a few reports of it working fine for you first. (I update from their repository from time to time, and all has been well here.)

Nov. 8, 2012

'#' in file url

by jcid＠dillo.org

On Wed, Nov 07, 2012 at 08:05:54PM +0000, corvid wrote: > Jorge wrote: > > On Wed, Nov 07, 2012 at 05:41:12PM +0000, corvid wrote: > > > Jorge wrote: > > > > On Wed, Nov 07, 2012 at 03:20:20AM +0000, corvid wrote: > > > > > > > > > > I had two files with '#' in their names that I wanted to view -- > > > > > file#1.png and file#2.png -- and dillo showed me the same file in > > > > > each tab. > > > > > > > > That's because '#' is not a valid character inside a URL. > > > [snip] > > > > i.e. anything after '#' is a 'fragment'. > > > > > > > > and BTW, that's why the file dpi escapes '#' as '%23' to be able > > > > to show the file. > > > > > > Right, it may be %23 at some point in its journey, but it's back to > > > '#' eventually -- and breaks. > > > > I tried: > > > > $ echo "hello" > /tmp/a#b > > $ dillo /tmp > > <click on the file link> > > > > and it works. > > If you make two files, a#1 and a#2, then run > dillo a#1 a#2 > you won't be shown two different files. Please check the committed patch. -- Cheers Jorge.-

Nov. 8, 2012

hyphenation in dillo

by corvid＠lavabit.com

Sebastian wrote: > On Mon, Sep 10, corvid wrote: > > I was looking at the src for http://distrowatch.com , and the > > source page is very wide -- wider than any lines, so far as I > > could see. > > There is one line, which is very long (number 54), but the current > release breaks this line into multiple ones. Can someone provide > details about the vsource plugin? The vsource page has <style type="text/css">PRE {white-space: pre-wrap} and the css2 spec says "If 'white-space' is set to 'pre' or 'pre-wrap', any sequence of spaces (U+0020) unbroken by an element boundary is treated as a sequence of non-breaking spaces. However, for 'pre-wrap', a line breaking opportunity exists at the end of the sequence."

Nov. 7, 2012

hyphenation in dillo

by sgeerken＠dillo.org

On Mon, Sep 10, corvid wrote: > I was looking at the src for http://distrowatch.com , and the > source page is very wide -- wider than any lines, so far as I > could see. There is one line, which is very long (number 54), but the current release breaks this line into multiple ones. Can someone provide details about the vsource plugin? Sebastian

Nov. 7, 2012

hyphenation in dillo

by sgeerken＠dillo.org

On Wed, Oct 31, corvid wrote: > With tip, I can't see the option in: > > <div> > <select> > <option value="100">object</option> > </select> > </div> > > With a dillo that I have around from right before the hyphenation merge, > the option appears. Fixed. Sebastian

Nov. 7, 2012

'#' in file url

by corvid＠lavabit.com

Jorge wrote: > On Wed, Nov 07, 2012 at 05:41:12PM +0000, corvid wrote: > > Jorge wrote: > > > On Wed, Nov 07, 2012 at 03:20:20AM +0000, corvid wrote: > > > > > > > > I had two files with '#' in their names that I wanted to view -- > > > > file#1.png and file#2.png -- and dillo showed me the same file in > > > > each tab. > > > > > > That's because '#' is not a valid character inside a URL. > > [snip] > > > i.e. anything after '#' is a 'fragment'. > > > > > > and BTW, that's why the file dpi escapes '#' as '%23' to be able > > > to show the file. > > > > Right, it may be %23 at some point in its journey, but it's back to > > '#' eventually -- and breaks. > > I tried: > > $ echo "hello" > /tmp/a#b > $ dillo /tmp > <click on the file link> > > and it works. If you make two files, a#1 and a#2, then run dillo a#1 a#2 you won't be shown two different files.

Nov. 7, 2012

'#' in file url

by jcid＠dillo.org

On Wed, Nov 07, 2012 at 05:41:12PM +0000, corvid wrote: > Jorge wrote: > > On Wed, Nov 07, 2012 at 03:20:20AM +0000, corvid wrote: > > > > > > I had two files with '#' in their names that I wanted to view -- > > > file#1.png and file#2.png -- and dillo showed me the same file in > > > each tab. > > > > That's because '#' is not a valid character inside a URL. > [snip] > > i.e. anything after '#' is a 'fragment'. > > > > and BTW, that's why the file dpi escapes '#' as '%23' to be able > > to show the file. > > Right, it may be %23 at some point in its journey, but it's back to > '#' eventually -- and breaks. I tried: $ echo "hello" > /tmp/a#b $ dillo /tmp <click on the file link> and it works. -- Cheers Jorge.-

Nov. 7, 2012

' and xhtml

by jcid＠dillo.org

On Wed, Nov 07, 2012 at 05:50:44PM +0000, corvid wrote: > Jorge wrote: > > On Mon, Nov 05, 2012 at 11:53:06PM +0000, corvid wrote: > > > > > > Jeremy wanted to add apos a long time ago, and it didn't happen then, > > > but we did give in and accept application/xhtml+xml--let's see--two > > > years ago now, so I wonder whether conditions have changed. > > > > Yep, things change in time... > > > > Although HTML 4.01 and other SPECS never succeeded to the point > > of making serving valid HTML/XHTML a rule of thumb, or best > > practice, things seem to have improved a bit since our early days > > (just my perception out of finding more and more dillo-readable > > sites these days). > > > > Escaping ' as APOS finds a solid reason in server contexts > > where there's a need to accept untrusted input for scripts or > > databases. > > > > I'd say, +1, feel free to commit. > > > > > > PS: Please post a sample URL. Just to get the feel of it. ;) > > It was brought to mind when I couldn't retrieve mail the other day > and checked http://lavabit.com . One of the news bits says > "We've updated our SSL certificate." > > > > Hmmm.... looking at the source now, I see that, on one hand, it has > > <?xml version="1.0" encoding="utf-8"?> > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> > > ..but, on the other hand, it says > > <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> > > ..instead of application/xhtml+xml. Yes, that's the state of things these days... There's almost no other way than heuristics -- Cheers Jorge.-

Nov. 7, 2012

' and xhtml

by corvid＠lavabit.com

Jorge wrote: > On Mon, Nov 05, 2012 at 11:53:06PM +0000, corvid wrote: > > > > Jeremy wanted to add apos a long time ago, and it didn't happen then, > > but we did give in and accept application/xhtml+xml--let's see--two > > years ago now, so I wonder whether conditions have changed. > > Yep, things change in time... > > Although HTML 4.01 and other SPECS never succeeded to the point > of making serving valid HTML/XHTML a rule of thumb, or best > practice, things seem to have improved a bit since our early days > (just my perception out of finding more and more dillo-readable > sites these days). > > Escaping ' as APOS finds a solid reason in server contexts > where there's a need to accept untrusted input for scripts or > databases. > > I'd say, +1, feel free to commit. > > > PS: Please post a sample URL. Just to get the feel of it. ;) It was brought to mind when I couldn't retrieve mail the other day and checked http://lavabit.com . One of the news bits says "We've updated our SSL certificate." Hmmm.... looking at the source now, I see that, on one hand, it has <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> ..but, on the other hand, it says <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ..instead of application/xhtml+xml.

Nov. 7, 2012

'#' in file url

by corvid＠lavabit.com

Jorge wrote: > On Wed, Nov 07, 2012 at 03:20:20AM +0000, corvid wrote: > > > > I had two files with '#' in their names that I wanted to view -- > > file#1.png and file#2.png -- and dillo showed me the same file in > > each tab. > > That's because '#' is not a valid character inside a URL. [snip] > i.e. anything after '#' is a 'fragment'. > > and BTW, that's why the file dpi escapes '#' as '%23' to be able > to show the file. Right, it may be %23 at some point in its journey, but it's back to '#' eventually -- and breaks.

Nov. 7, 2012