- Dillo-dev - lists.mailman3.com

Typing Bug when moving Dillo on DWM's Virtual Desktops

by rogerx＠sdf.lonestar.org

I'm finally tackling a typing bug with Dillo, and have found it occurs when moving the Dillo browser to DMW's other virtual desktops. It doesn't occur when Dillo is first started. Nothing, if anything at all, shows within gdb. And, I can't really get to the debug output of DWM as I'm running nvidia proprietary drivers which blanks the terminal once X is started. I do have a laptop for which I can further investigate the DWM debug data, but figured I should post what I know to see if any of you notice similar. The basic bug scenario, move the Dillo browser to another Virtual Desktop within DWM and start typing (within the url field or within the Google search field.) I notice only certain keys type their characters and most others will either type nothing or may clear the entire field (ie. clear line) Possible a meta key sticks when moving the browser to another desktop?? -- Roger http://rogerx.freeshell.org

Sept. 26, 2009

[patch]: fix the meta-refresh warning code

by jcid＠dillo.org

On Fri, Sep 25, 2009 at 06:15:05PM +0000, corvid wrote: > Jorge wrote: > > On Fri, Sep 25, 2009 at 07:16:12AM -0400, Jorge Arellano Cid wrote: > > > On Thu, Sep 24, 2009 at 06:04:15AM +0100, Jeremy Henty wrote: > > > > On Tue, Sep 22, 2009 at 02:25:47PM -0400, Jorge Arellano Cid wrote: > > > > > On Tue, Sep 22, 2009 at 04:35:28PM +0000, corvid wrote: > > > > > > > > > > Would it be less trouble to have this widget as a child of the UI > > > > > > instead of in the rendering area? (I sort of had the impression > > > > > > that was the plan... > > > > > > > > > > That's exactly the plan. > > > > > > > > > > A simple fltk widget that hides/shows (as the findext bar) and > > > > > that gives a text message. It should also support a fake HTML link > > > > > (underlined word that reacts to left click). > > > > > > > > Ah, I think I misunderstood the reference to "custom widget" in the TO > > > > DO note. I was fixated on the Dillo Widget system and didn't realise > > > > it was talking about a new FLTK widget. Maybe my patch isn't the way > > > > to go. Still, it would be nice for the custom widget to be properly > > > > CSS-styled. Maybe it be could another FltkViewport? > > > > > > As this is part of the UI, I'd suggest to use Xdefaults as > > > Johannes suggested for colors some time ago. > > > > Ehmmm, by "Xdefaults", I mean the default X resource files. > > ISTR that the latest was that Johannes was trying > to get the FLTKers to enable the relevant code that > had been commented out (rather than having dillo > do it directly), but nothing happened on the fltk side. FLTK2 is dead (that's almost official). Progress will happen in 1.3.x branch (or whatever they chose to call a new branch merging FLTK2 and 1.3.x [1]). In the meanwhile, I'd be OK with a non-themeable warning widget with the same colors it used to have. ;-) FWIW: the patch should implement an fltk widget as described in a previous email. So, no further work on the proposed patch is necessary. [1] http://fltk.org/newsgroups.php?s7257+gfltk.development+v7263+T0 -- Cheers Jorge.-

Sept. 25, 2009

[patch]: fix the meta-refresh warning code

by corvid＠lavabit.com

Jorge wrote: > On Fri, Sep 25, 2009 at 07:16:12AM -0400, Jorge Arellano Cid wrote: > > On Thu, Sep 24, 2009 at 06:04:15AM +0100, Jeremy Henty wrote: > > > On Tue, Sep 22, 2009 at 02:25:47PM -0400, Jorge Arellano Cid wrote: > > > > On Tue, Sep 22, 2009 at 04:35:28PM +0000, corvid wrote: > > > > > > > > Would it be less trouble to have this widget as a child of the UI > > > > > instead of in the rendering area? (I sort of had the impression > > > > > that was the plan... > > > > > > > > That's exactly the plan. > > > > > > > > A simple fltk widget that hides/shows (as the findext bar) and > > > > that gives a text message. It should also support a fake HTML link > > > > (underlined word that reacts to left click). > > > > > > Ah, I think I misunderstood the reference to "custom widget" in the TO > > > DO note. I was fixated on the Dillo Widget system and didn't realise > > > it was talking about a new FLTK widget. Maybe my patch isn't the way > > > to go. Still, it would be nice for the custom widget to be properly > > > CSS-styled. Maybe it be could another FltkViewport? > > > > As this is part of the UI, I'd suggest to use Xdefaults as > > Johannes suggested for colors some time ago. > > Ehmmm, by "Xdefaults", I mean the default X resource files. ISTR that the latest was that Johannes was trying to get the FLTKers to enable the relevant code that had been commented out (rather than having dillo do it directly), but nothing happened on the fltk side.

Sept. 25, 2009

Weird chars bug

by corvid＠lavabit.com

Jorge wrote: > Since dillo-2.1, enabled-CSS makes funny chars in this page: > > http://blogdrake.net/node/14916 > > Screenshot: > > http://www.dillo.org/test/weirdChars.jpg > > Disabling it from the tools button solves the problem. > Does anybody know what's the problem here? I suspect it has something to do with the font: 76% Trebuchet MS, Verdana, Arial, Helvetica, sans-serif; in http://blogdrake.net/themes/lightdrake/style.css Of course with my general paucity of fonts, it looks fine to me :)

Sept. 25, 2009

[patch]: fix the meta-refresh warning code

by jcid＠dillo.org

On Fri, Sep 25, 2009 at 07:16:12AM -0400, Jorge Arellano Cid wrote: > On Thu, Sep 24, 2009 at 06:04:15AM +0100, Jeremy Henty wrote: > > On Tue, Sep 22, 2009 at 02:25:47PM -0400, Jorge Arellano Cid wrote: > > > On Tue, Sep 22, 2009 at 04:35:28PM +0000, corvid wrote: > > > > > > Would it be less trouble to have this widget as a child of the UI > > > > instead of in the rendering area? (I sort of had the impression > > > > that was the plan... > > > > > > That's exactly the plan. > > > > > > A simple fltk widget that hides/shows (as the findext bar) and > > > that gives a text message. It should also support a fake HTML link > > > (underlined word that reacts to left click). > > > > Ah, I think I misunderstood the reference to "custom widget" in the TO > > DO note. I was fixated on the Dillo Widget system and didn't realise > > it was talking about a new FLTK widget. Maybe my patch isn't the way > > to go. Still, it would be nice for the custom widget to be properly > > CSS-styled. Maybe it be could another FltkViewport? > > As this is part of the UI, I'd suggest to use Xdefaults as > Johannes suggested for colors some time ago. Ehmmm, by "Xdefaults", I mean the default X resource files. -- Cheers Jorge.-

Sept. 25, 2009

Weird chars bug

by jcid＠dillo.org

Hi, Since dillo-2.1, enabled-CSS makes funny chars in this page: http://blogdrake.net/node/14916 Screenshot: http://www.dillo.org/test/weirdChars.jpg Disabling it from the tools button solves the problem. Does anybody know what's the problem here? -- Cheers Jorge.-

Sept. 25, 2009

[patch]: fix the meta-refresh warning code

by jcid＠dillo.org

On Thu, Sep 24, 2009 at 06:04:15AM +0100, Jeremy Henty wrote: > On Tue, Sep 22, 2009 at 02:25:47PM -0400, Jorge Arellano Cid wrote: > > On Tue, Sep 22, 2009 at 04:35:28PM +0000, corvid wrote: > > > > Would it be less trouble to have this widget as a child of the UI > > > instead of in the rendering area? (I sort of had the impression > > > that was the plan... > > > > That's exactly the plan. > > > > A simple fltk widget that hides/shows (as the findext bar) and > > that gives a text message. It should also support a fake HTML link > > (underlined word that reacts to left click). > > Ah, I think I misunderstood the reference to "custom widget" in the TO > DO note. I was fixated on the Dillo Widget system and didn't realise > it was talking about a new FLTK widget. Maybe my patch isn't the way > to go. Still, it would be nice for the custom widget to be properly > CSS-styled. Maybe it be could another FltkViewport? As this is part of the UI, I'd suggest to use Xdefaults as Johannes suggested for colors some time ago. -- Cheers Jorge.-

Sept. 25, 2009

[patch]: fix the meta-refresh warning code

by onepoint＠starurchin.org

On Tue, Sep 22, 2009 at 02:25:47PM -0400, Jorge Arellano Cid wrote: > On Tue, Sep 22, 2009 at 04:35:28PM +0000, corvid wrote: > > Would it be less trouble to have this widget as a child of the UI > > instead of in the rendering area? (I sort of had the impression > > that was the plan... > > That's exactly the plan. > > A simple fltk widget that hides/shows (as the findext bar) and > that gives a text message. It should also support a fake HTML link > (underlined word that reacts to left click). Ah, I think I misunderstood the reference to "custom widget" in the TO DO note. I was fixated on the Dillo Widget system and didn't realise it was talking about a new FLTK widget. Maybe my patch isn't the way to go. Still, it would be nice for the custom widget to be properly CSS-styled. Maybe it be could another FltkViewport? Regards, Jeremy Henty

Sept. 24, 2009

[patch]: fix the meta-refresh warning code

by jcid＠dillo.org

On Tue, Sep 22, 2009 at 04:35:28PM +0000, corvid wrote: > Johannes wrote: > > On Tue, Sep 22, 2009 at 07:47:09AM +0100, Jeremy Henty wrote: > > > On Mon, Sep 21, 2009 at 11:58:09PM -0400, Jorge Arellano Cid wrote: > > > > > > > > * The HTML parser in table.cc does not create table widgets if > > > > > USE_TABLES is not defined. Perhaps this code should do the > > > > > same? > > > > > > > > Not necessary. That was an old feature for narrow displays. > > > > > > In that case, shouldn't we remove USE_TABLES entirely? > > > > > > > > * It would be nice if the widgets and the redirect link were > > > > > styled from the User Agent style in css.cc . ... > > > > > > > > AFAIS, the warning widget needs its own scheme, like the rest of > > > > the panel. > > > > > > Perhaps we could extend the default style in css.cc with clauses like > > > "dillo meta-refresh-warning redirect { color: ... }", using "dillo" > > > as a reserved CSS class for internal use? Then all of the style > > > information would be in CSS and none of it would be hard-coded in the > > > parser, which is how it should be. > > > > Yes, this would be possible. Other browsers also have similar > > extensions. They seem to start with a '-' usually ("-webkit...", > > "-moz..."). > > But generally if we generate messages in the rendering area, we > > can't avoid that someone fakes them on his webpage. > > Would it be less trouble to have this widget as a child of the UI > instead of in the rendering area? (I sort of had the impression that > was the plan, but maybe that was the xhtml one, or maybe I'm just > mixed up.) That's exactly the plan. A simple fltk widget that hides/shows (as the findext bar) and that gives a text message. It should also support a fake HTML link (underlined word that reacts to left click). Sorry for not having the time yet to test the code... -- Cheers Jorge.-

Sept. 22, 2009

[patch]: fix the meta-refresh warning code

by corvid＠lavabit.com

Johannes wrote: > On Tue, Sep 22, 2009 at 07:47:09AM +0100, Jeremy Henty wrote: > > On Mon, Sep 21, 2009 at 11:58:09PM -0400, Jorge Arellano Cid wrote: > > > > > > * The HTML parser in table.cc does not create table widgets if > > > > USE_TABLES is not defined. Perhaps this code should do the > > > > same? > > > > > > Not necessary. That was an old feature for narrow displays. > > > > In that case, shouldn't we remove USE_TABLES entirely? > > > > > > * It would be nice if the widgets and the redirect link were > > > > styled from the User Agent style in css.cc . ... > > > > > > AFAIS, the warning widget needs its own scheme, like the rest of > > > the panel. > > > > Perhaps we could extend the default style in css.cc with clauses like > > "dillo meta-refresh-warning redirect { color: ... }", using "dillo" > > as a reserved CSS class for internal use? Then all of the style > > information would be in CSS and none of it would be hard-coded in the > > parser, which is how it should be. > > Yes, this would be possible. Other browsers also have similar > extensions. They seem to start with a '-' usually ("-webkit...", > "-moz..."). > But generally if we generate messages in the rendering area, we > can't avoid that someone fakes them on his webpage. Would it be less trouble to have this widget as a child of the UI instead of in the rendering area? (I sort of had the impression that was the plan, but maybe that was the xhtml one, or maybe I'm just mixed up.)

Sept. 22, 2009