- Dillo-dev - lists.mailman3.com

What's pending for RC2

by jcid＠dillo.org

Hi, [ok] new-tab and window title [ok] CSS adjacent sibling selectors [ ] default search engine [ ] margin-bottom > [ ] default search engine > I've been using search_url="http://duckduckgo.com/lite/?kp=-1&q=%s" > and it works quite well for me. > Please vote. > me: +1 for making it the default > > Also I'd like to add some default search engines. For instance, > this one is very useful for me: > search_url="Free Dictionary http://www.thefreedictionary.com/%s" > Comments/suggestions? Last chance to vote... > [ ] margin-bottom In evaluation stage. -- Cheers Jorge.-

Aug. 26, 2011

margin-bottom counted twice

by Johannes.Hofmann＠gmx.de

On Fri, Aug 26, 2011 at 04:21:04PM +0000, corvid wrote: > Johannes wrote: > > I'm not 100% sure about removing the "if" in Textblock::wordWrap(), > > but why shouldn't a widget's top margin count in the first line of a > > paragraph? > > My first thought was that maybe it has something to do with cases like > > <div style="margin-top: 100px"> > <div style="margin-top: 100px"> > <img src="http://www.dillo.org/wearlab.png" style="margin-top: 100px"> > </div> > </div> > > where I was thinking those were all supposed to collapse. I haven't looked > into the spec at all yet, but we get a total of 300px on dillo, and firefox > has the divs collapse and the img margin is separate (maybe a block/inline > distinction?). seems so. changing it to <img src="http://www.dillo.org/wearlab.png" style="display: block; margin-top: 100px"> causes firefox to also collapse the img margin. I have margin collapsing also on my list.

Aug. 26, 2011

problems with very long alt text

by jcid＠dillo.org

On Fri, Aug 26, 2011 at 07:29:21PM +0200, hiro wrote: > With tinycorelinux and Xorg-7.5 i915 on 1024x768 I get a completely > garbled screen and unresponsive system, CPU ran hot and I had to > reboot. > I can reboot into VESA if you want. [later hiro wrote:] > Ok I don't get the bug with Xvesa, tinycorelinux' default Xserver. Excellent! This proves the point (AFAICS). Thank you very much. -- Cheers Jorge.-

Aug. 26, 2011

margin-bottom counted twice

by jcid＠dillo.org

On Fri, Aug 26, 2011 at 10:20:43AM +0200, Johannes Hofmann wrote: > Hi, > > I found that current dillo uses twice the given > margin-bottom: value. See attached margin_bottom.html. > It is related to commented out code in textblock.cc. > Attached patch tries to fix it while not breaking the test cases in > http://www.dillo.org/test/img/ > I'm not 100% sure about removing the "if" in Textblock::wordWrap(), > but why shouldn't a widget's top margin count in the first line of a > paragraph? AFAIR there was the "line1" offset stuff (which seem not to apply here because it's horizontal), and the handOverBreak() code which dealt with spacing between textblocks. I'm for applying the patch, but would give first a second look to handOverBreak() just to be sure. BTW, after a quick review it looks weird, as the value seems inherited (copied from previous stack object) most of the time... -- Cheers Jorge.-

Aug. 26, 2011

margin-bottom counted twice

by corvid＠lavabit.com

Johannes wrote: > I'm not 100% sure about removing the "if" in Textblock::wordWrap(), > but why shouldn't a widget's top margin count in the first line of a > paragraph? My first thought was that maybe it has something to do with cases like <div style="margin-top: 100px"> <div style="margin-top: 100px"> <img src="http://www.dillo.org/wearlab.png" style="margin-top: 100px"> </div> </div> where I was thinking those were all supposed to collapse. I haven't looked into the spec at all yet, but we get a total of 300px on dillo, and firefox has the divs collapse and the img margin is separate (maybe a block/inline distinction?).

Aug. 26, 2011

problems with very long alt text

by jcid＠dillo.org

On Fri, Aug 26, 2011 at 12:47:24PM -0300, Jorge Arellano Cid wrote: > On Fri, Aug 26, 2011 at 04:51:53PM +0300, Rogut??s Sparnuotos wrote: > > > try booting with the 'i915.modeset=0' kernel parameter? > > It made no difference :-P Actually it made a difference. I can't change the resolution without the kernel argument. Thanks. BTW, although my custom xorg.conf says: Section "Device" Identifier "Card0" Driver "vesa" BusID "PCI:0:2:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" SubSection "Display" Viewport 0 0 Depth 16 Modes "800x600" "1024x768" EndSubSection EndSection ... lsmod shows i915 is loaded. -- Cheers Jorge.-

Aug. 26, 2011

problems with very long alt text

by johannes.hofmann＠gmx.de

On Fri, Aug 26, 2011 at 12:47:24PM -0300, Jorge Arellano Cid wrote: > On Fri, Aug 26, 2011 at 04:51:53PM +0300, Rogut??s Sparnuotos wrote: > > Jorge Arellano Cid (2011-08-26 09:34): > > > I can't get this Debian to go VESA. Hints welcomed. > > > > Perhaps make sure that you have the 'xserver-xorg-video-vesa' package > > It is there. > > > and > > try booting with the 'i915.modeset=0' kernel parameter? > > It made no difference :-P > > > But probably it is > > more stubborn than that, e.g. only the i915 driver knows how to initialize > > enough video RAM for the native resolution. > > I have a "Tiny Core" linux live CD that works without the intel > driver (AFAICT). No native resolution though. > > > > In such a case running > > `X -depth 8` could work, but delving any deeper is probably not worth the > > trouble. > > This gave me an idea, and guess what, if I run with the same > kernel/intel-driver that crashes but with a different resolution > (1024x768) there's no crash. > > Now, if VESA can't do the native resolution, I don't know how > to get closer to a proof of a bug in the i915 driver. Maybe with http://sourceforge.net/projects/xtrace/ you can determine the problematic X11 request. I can't reproduce the crash btw. Cheers, Johannes

Aug. 26, 2011

problems with very long alt text

by jcid＠dillo.org

On Fri, Aug 26, 2011 at 04:51:53PM +0300, Rogut??s Sparnuotos wrote: > Jorge Arellano Cid (2011-08-26 09:34): > > I can't get this Debian to go VESA. Hints welcomed. > > Perhaps make sure that you have the 'xserver-xorg-video-vesa' package It is there. > and > try booting with the 'i915.modeset=0' kernel parameter? It made no difference :-P > But probably it is > more stubborn than that, e.g. only the i915 driver knows how to initialize > enough video RAM for the native resolution. I have a "Tiny Core" linux live CD that works without the intel driver (AFAICT). No native resolution though. > In such a case running > `X -depth 8` could work, but delving any deeper is probably not worth the > trouble. This gave me an idea, and guess what, if I run with the same kernel/intel-driver that crashes but with a different resolution (1024x768) there's no crash. Now, if VESA can't do the native resolution, I don't know how to get closer to a proof of a bug in the i915 driver. -- Cheers Jorge.-

Aug. 26, 2011

problems with very long alt text

by rogutes＠googlemail.com

Jorge Arellano Cid (2011-08-26 09:34): > I can't get this Debian to go VESA. Hints welcomed. Perhaps make sure that you have the 'xserver-xorg-video-vesa' package and try booting with the 'i915.modeset=0' kernel parameter? But probably it is more stubborn than that, e.g. only the i915 driver knows how to initialize enough video RAM for the native resolution. In such a case running `X -depth 8` could work, but delving any deeper is probably not worth the trouble. > It looks like an intel driver bug as corvid suggested. No crashes here with dillo3-tip and the radeon driver. -- -- Rogut?s Sparnuotos

Aug. 26, 2011

problems with very long alt text

by jcid＠dillo.org

On Thu, Aug 25, 2011 at 09:12:17PM -0300, Jorge Arellano Cid wrote: > On Thu, Aug 25, 2011 at 10:53:50PM +0000, corvid wrote: > > furaisanjin wrote: > > > 2011/8/26 corvid <corvid(a)lavabit.com>: > > > > I just tried running from my older slackware-13.1 partition and there > > > > was no memory-eating! > > > > > > I don't have any issue on FreeBSD 8.2. it sounds like particular linux > > > libc or kernel issue. > > > > Jorge: Do you use the Intel x.org driver as well? It is notoriously and > > chronically buggy, despite(?) being written by Intel guys, and maybe > > that's it. > > Yes! > > This notebook has it and the kernel loads "i915". Will try "vesa"... So far, it works on FreeBSD 8.2, also for corvid with vesa, and for me in another computer with ATI video, and in my same notebook with intel drivers but from linux-2.6.32.31 times. I can't get this Debian to go VESA. Hints welcomed. It looks like an intel driver bug as corvid suggested. -- Cheers Jorge.-

Aug. 26, 2011