- Dillo-dev - lists.mailman3.com

domainrc to manage cross-domain requests (was Re: RequestPolicy-like patch)

by corvid＠lavabit.com

p37sitdu wrote: > You did not remove filter_auto_requests preference (see my patch [1]). I thought I'd removed all of it; did I overlook something?

Oct. 4, 2012

domainrc to manage cross-domain requests (was Re: RequestPolicy-like patch)

by p37sitdu＠lavabit.com

On Wed, Oct 03, 2012 at 02:04:45AM +0000, corvid wrote: > Committed with a little dilloification, etc. You did not remove filter_auto_requests preference (see my patch [1]). It is not necessary: no domainrc can work as filter_auto_requests=allow_all and when domainrc with "default deny" is present it is the same as filter_auto_requests=same_domain. [1] http://lists.auriga.wearlab.de/pipermail/dillo-dev/2012-August/009394.html

Oct. 3, 2012

domainrc to manage cross-domain requests (was Re: RequestPolicy-like patch)

by corvid＠lavabit.com

I should mention that I was playing around with printing a summary at freeall time in order to see which sites are the worst offenders. Diff attached.

Oct. 3, 2012

domainrc to manage cross-domain requests (was Re: RequestPolicy-like patch)

by corvid＠lavabit.com

p37sitdu wrote: > Patch implements functions similar to Firefox addon RequestPolicy. [1] > It allows user to control automatic requests more flexible than > filter_auto_requests option. Patch removes this option and replaces it > with file .dillo/domainrc that looks like this: > > default deny > wikipedia.org .wikimedia.org > wikisource.org .wikimedia.org > wikitionary.org .wikimedia.org > wikiversity.org .wikimedia.org > > That way most requests are denied, but images on wikipedia are loaded > from wikimedia.org without clicking on them. > > Patterns can start with "." to allow subdomains. > > Special pattern "*" can be used to allow requests to any domains from > some domain (for example if it is a website full of external images) or > to allow requests from any domain to some domain (maybe CDN). > > Without domainrc file all cross-domain requests are denied. > > [1] https://www.requestpolicy.com/ Committed with a little dilloification, etc. At the moment, I have the default set to accept rather than deny, thinking that it might be easier for us to build up a sample or default domainrc with a bunch of notorious ad sites to blacklist than it would be to whitelist enough common sites that use a [site]images.com or suchlike.

Oct. 3, 2012

Key binding for viewing page source

by corvid＠lavabit.com

Jorge wrote: > On Thu, Sep 20, 2012 at 08:45:08PM +0200, Johannes Hofmann wrote: > > On Wed, Sep 19, 2012 at 09:06:22PM +0000, corvid wrote: > > > Alexander wrote: > > > > I use the "view page source" function from the right-click popup menu > > > > very often and so I created a key binding for this (see attached > > > > patch). Since I find this very handy, please consider this patch for > > > > the repository. > > > > > > This would be good to have. > > > > I'd also like to have that feature. > > +1 Committed.

Sept. 28, 2012

hyphenation in dillo

by corvid＠lavabit.com

The borders on the "Search results" and "Nutrient values" boxes are overlapping on http://www.bitelog.com/mega-food-search.htm?q=masa

Sept. 27, 2012

hyphenation in dillo

by sgeerken＠dillo.org

On Wed, Sep 26, Jorge Arellano Cid wrote: > On Fri, Sep 14, 2012 at 12:38:46PM +0200, Sebastian Geerken wrote: > > On Thu, Sep 13, Alexander Voigt wrote: > > > On Mon, Sep 10, 2012 at 08:45:22PM +0200, Sebastian Geerken wrote: > > > > No, not yet. BTW: I haven't understood whether "xml:" is a normal > > > > namespace prefix (for which namespace?) or is specialy reserved (and > > > > may so not be used as namespace prefix). In the latter case, support > > > > would be rather simple. > > > > > > As written in [1], the "xml:" prefix is bound to the namespace > > > http://www.w3.org/XML/1998/namespace , which is reseved for the W3C. > > > This means that the nobody, except the W3C, can reuse this prefix for > > > their own namespace. > > > > > > So, as long as the meaning of "xml:lang" does not change (which is > > > very unlikely), it can be interpreted in the same way as the "lang" > > > attribute. > > > > So, this simple patch (or similar): > > > > ---------------------------------------------------------------------- > > [...] > > ---------------------------------------------------------------------- > > > > would work, without bothering about XML namespaces (in the near > > future). What do the other developers think? > > Yes, it looks OK to me. > > I'd go with the attached patch (a bit more explicit, +comments) > > Feel free to commit. Done. Sebastian

Sept. 27, 2012

hyphenation in dillo

by jcid＠dillo.org

Hi Sebastian, On Fri, Sep 14, 2012 at 12:38:46PM +0200, Sebastian Geerken wrote: > On Thu, Sep 13, Alexander Voigt wrote: > > On Mon, Sep 10, 2012 at 08:45:22PM +0200, Sebastian Geerken wrote: > > > No, not yet. BTW: I haven't understood whether "xml:" is a normal > > > namespace prefix (for which namespace?) or is specialy reserved (and > > > may so not be used as namespace prefix). In the latter case, support > > > would be rather simple. > > > > As written in [1], the "xml:" prefix is bound to the namespace > > http://www.w3.org/XML/1998/namespace , which is reseved for the W3C. > > This means that the nobody, except the W3C, can reuse this prefix for > > their own namespace. > > > > So, as long as the meaning of "xml:lang" does not change (which is > > very unlikely), it can be interpreted in the same way as the "lang" > > attribute. > > So, this simple patch (or similar): > > ---------------------------------------------------------------------- > diff -r d0a8d2a5ede3 src/html.cc > --- a/src/html.cc Thu Sep 13 12:35:54 2012 +0200 > +++ b/src/html.cc Fri Sep 14 12:35:38 2012 +0200 > @@ -3448,6 +3448,15 @@ > html->styleEngine->setNonCssHint(PROPERTY_X_LANG, > CSS_TYPE_STRING, > attrbuf); > } > + > + if (tagsize >= 14) { /* TODO prefs.hyphenate? */ > + /* length of "<t xml:lang=i>" */ > + attrbuf = Html_get_attr2(html, tag, tagsize, "xml:lang", > + HTML_LeftTrim | HTML_RightTrim); > + if (attrbuf) > + html->styleEngine->setNonCssHint(PROPERTY_X_LANG, > CSS_TYPE_STRING, > + attrbuf); > + } > } > > static void Html_display_block(DilloHtml *html) > ---------------------------------------------------------------------- > > would work, without bothering about XML namespaces (in the near > future). What do the other developers think? Yes, it looks OK to me. I'd go with the attached patch (a bit more explicit, +comments) Feel free to commit. -- Cheers Jorge.-

Sept. 26, 2012

Doxyfile

by sgeerken＠dillo.org

On Sun, May 27, 123 wrote: > By the way new Doxygen supports Markdown[1] and it is enabled by > default. It is easier to read and write than HTML. index.doc rewritten > using markdown is attached. Existing documentation (especially .txt > files) can be converted to markdown too. > > [1] http://daringfireball.net/projects/markdown/ Yes, this looks interesting, and I've started new documentation using Markdown (in the floats repository). Although I do not plan to convert the existing documentations, at least as long as there are different repositories to merge. Thank you for the hint. Sebastian

Sept. 26, 2012

Key binding for viewing page source

by Hole.destructor＠gmx.de

Hi. Jeremy Henty wrote: > Jorge Arellano Cid wrote: > > > BTW, as you use viewsource very often, what do you like best for > > displayed HTML lines, one long scrollable line or wrapping? > > Pardon me for butting in here, but I use view source quite a lot and I > would definitely prefer wrapping. (Is wrapping supported at the > moment?) Many Web sites ship HTML with absurdly long lines which > makes viewing their source practically impossible - horizontal > scrolling is very little help when the line is around 50 screen widths > long (sadly this is not an exaggeration). I also like line wrapping more than scrolling horizontally. When you want to read the HTML code with long lines, it is more convenient to have only one scrolling direction (vertically) instead of two (vertically + horizontally). Best, Alex

Sept. 23, 2012