October 2008 - Dillo-dev - lists.mailman3.com

feature freeze

by onepoint＠starurchin.org

On Thu, Oct 02, 2008 at 02:01:35PM -0400, Jorge Arellano Cid wrote: > OK, so we have: Dillo won't let me login to Wikipedia! Of course this may be a *good* thing. :-) After making the MSG a little more verbose (patch attached) it reports that it is rejecting the HttpOnly attribute (log attached). I *think* this attribute is a security feature to avoid hacks that trick your browser into relaying cookie info from an http connection to an https connection. What should dillo do here? No matter what dillo should do, I think this diagnostics patch is good because it makes the MSG far more useful. Regards, Jeremy Henty

Oct. 2, 2008

feature freeze

by onepoint＠starurchin.org

On Thu, Oct 02, 2008 at 08:01:58PM +0200, Johannes Hofmann wrote: > 6.- redraw storms related to the MenuTabPager (noticed by Jeremy) > [...] > 6: Using the ShrinkTabPager avoids the problem Here's a (tiny) patch to use the ShrinkTabPager . Personally I find dillo almost unusable without it, but that may be because I like to open lots of tabs. Regards, Jeremy Henty

Oct. 2, 2008

crash with reload and textarea

by Johannes.Hofmann＠gmx.de

On Thu, Oct 02, 2008 at 07:12:31PM +0000, corvid wrote: > It doesn't seem to want to break for me, but > I wonder whether it bears some similarity to > this whole deal with my pending callbacks: > http://lists.auriga.wearlab.de/pipermail/dillo-dev/2008-October/005000.html > Don't think so. The textarea thing turned out to be a small fltk2 bug: http://www.fltk.org/str.php?L2055 Cheers, Johannes

Oct. 2, 2008

patch: close windows from menubar

by corvid＠lavabit.com

BTW, I notice that ctrl-Q and alt-Q, listed in the menu, don't do anything.

Oct. 2, 2008

feature freeze

by corvid＠lavabit.com

I wrote: > WM decorations: Unfortunate, yeah. > I still use xwd. I don't know what people use nowadays. > Probably something heavyweight. Guess what? xwd has a -frame option. Sigh. I never even checked.

Oct. 2, 2008

feature freeze

by Johannes.Hofmann＠gmx.de

On Thu, Oct 02, 2008 at 06:27:11PM +0000, corvid wrote: > Jorge wrote: > > OK, so we have: > > > > 1.- the mini_bug.xpm FLTK2 fix. > > 2.- the focused textarea callback issue. > > 3.- Alt-X crash in the menu. > > 4.- hardcoded 128 tabs. > > 5.- leaving-the-window nav_expecting problem. > > > > > > Status: > > > > 1: There's a simple workaround. > > 2: Waiting for comment from Johannes. > > 3: There's a simple workaround. Valgrind may shed some light... > > We know the problem. No valgrind necessary. > http://lists.auriga.wearlab.de/pipermail/dillo-dev/2008-September/004981.ht… > > > 4: We may ship with dillo-hardcoded maxtabs. Right? > > 5: Doesn't happen with XFCE... Will test icewm and fvwm. > > > > > > BTW, I noticed the nice new screnshots. Good! > > From a purely aesthetic point of view, > > why are WM decorations left out? > > WM decorations: Unfortunate, yeah. > I still use xwd. I don't know what people use nowadays. > Probably something heavyweight. > dwm (www.suckless.org) wc -l dwm.c 1742 dwm.c :-) Cheers, Johannes

Oct. 2, 2008

feature freeze

by corvid＠lavabit.com

Jorge wrote: > OK, so we have: > > 1.- the mini_bug.xpm FLTK2 fix. > 2.- the focused textarea callback issue. > 3.- Alt-X crash in the menu. > 4.- hardcoded 128 tabs. > 5.- leaving-the-window nav_expecting problem. > > > Status: > > 1: There's a simple workaround. > 2: Waiting for comment from Johannes. > 3: There's a simple workaround. Valgrind may shed some light... We know the problem. No valgrind necessary. http://lists.auriga.wearlab.de/pipermail/dillo-dev/2008-September/004981.ht… > 4: We may ship with dillo-hardcoded maxtabs. Right? > 5: Doesn't happen with XFCE... Will test icewm and fvwm. > > > BTW, I noticed the nice new screnshots. Good! > From a purely aesthetic point of view, > why are WM decorations left out? WM decorations: Unfortunate, yeah. I still use xwd. I don't know what people use nowadays. Probably something heavyweight.

Oct. 2, 2008

feature freeze

by Johannes.Hofmann＠gmx.de

On Thu, Oct 02, 2008 at 02:01:35PM -0400, Jorge Arellano Cid wrote: > On Thu, Oct 02, 2008 at 05:44:32PM +0000, corvid wrote: > > Jorge wrote: > > > More or less we entered "feature freeze" mode implicitly. > > > > > > What is left pending? > > > > > > I remember: > > > > > > - the mini_bug.xpm FLTK2 fix. > > > - the focused textarea callback issue. > > > > My alt-X crash in the menu. I guess I'll look into giving it a timeout. > > > > I think the 128 tabs and some other hardcoded 128 in there that Johannes found > > are still there. > > > > My leaving-the-window nav_expecting problem would be nice if possible. > > OK, so we have: > > 1.- the mini_bug.xpm FLTK2 fix. > 2.- the focused textarea callback issue. > 3.- Alt-X crash in the menu. > 4.- hardcoded 128 tabs. > 5.- leaving-the-window nav_expecting problem. 6.- redraw storms related to the MenuTabPager (noticed by Jeremy) > > > Status: > > 1: There's a simple workaround. > 2: Waiting for comment from Johannes. > 3: There's a simple workaround. Valgrind may shed some light... > 4: We may ship with dillo-hardcoded maxtabs. Right? > 5: Doesn't happen with XFCE... Will test icewm and fvwm. > 6: Using the ShrinkTabPager avoids the problem Cheers, Johannes

Oct. 2, 2008

crash with reload and textarea

by Johannes.Hofmann＠gmx.de

On Thu, Oct 02, 2008 at 12:51:16PM -0400, Jorge Arellano Cid wrote: > On Thu, Oct 02, 2008 at 05:38:18PM +0200, Johannes Hofmann wrote: > > Hi, > > > > when using MALLOC_OPTIONS=GJPRZ on DragonFly which enables malloc > > debugging I get a crash when hitting Ctrl+r to reload a page with > > entered text in a textarea if the focus is still in the > > textarea. > > It seems that the Ctrl+r causes a callback on the already deleted > > fltk Input widget: > > There seems to be a bug in FLTK2's Input::replace(), > called by Input::insert(). > > The attached workaround solves it for me. Please check. No, that doesn't help. Perhaps I wasn't clear about the textarea thing. I meant something like: <html> <body> <form> <textarea></textarea> </form> </body> </html> On that page if I enter something, keep the focus in the textarea widget, hit Ctrl-r and then click somewhere I get the crash. Cheers, Johannes

Oct. 2, 2008

feature freeze

by jcid＠dillo.org

On Thu, Oct 02, 2008 at 05:44:32PM +0000, corvid wrote: > Jorge wrote: > > More or less we entered "feature freeze" mode implicitly. > > > > What is left pending? > > > > I remember: > > > > - the mini_bug.xpm FLTK2 fix. > > - the focused textarea callback issue. > > My alt-X crash in the menu. I guess I'll look into giving it a timeout. > > I think the 128 tabs and some other hardcoded 128 in there that Johannes found > are still there. > > My leaving-the-window nav_expecting problem would be nice if possible. OK, so we have: 1.- the mini_bug.xpm FLTK2 fix. 2.- the focused textarea callback issue. 3.- Alt-X crash in the menu. 4.- hardcoded 128 tabs. 5.- leaving-the-window nav_expecting problem. Status: 1: There's a simple workaround. 2: Waiting for comment from Johannes. 3: There's a simple workaround. Valgrind may shed some light... 4: We may ship with dillo-hardcoded maxtabs. Right? 5: Doesn't happen with XFCE... Will test icewm and fvwm. BTW, I noticed the nice new screnshots. Good! From a purely aesthetic point of view, why are WM decorations left out? -- Cheers Jorge.-

Oct. 2, 2008