March 2011 - Dillo-dev - lists.mailman3.com

big mistake with hg

by jcid＠dillo.org

On Thu, Mar 10, 2011 at 05:59:21PM +0100, Johannes Hofmann wrote: > On Thu, Mar 10, 2011 at 04:46:32PM +0000, Jorge Arellano Cid wrote: > > Hi there, > > > > I just pushed 120 changesets to hg "dillo" instead of "dillo_port1.3" > > by mistake (wrong default). > > > > Is there a simple way to clean the mess by purging the changes? > > If it's the last push to the "dillo" repo, you can run > hg rollback > on the master repo. Where's the master repo? (I can't find it in auriga). > Alternatively you can do > hg clone -r <last good revision> dillo dillo_purged > to create a new purged clone and then replace the master repo with > that. I don't have the last revision (haven't worked on 2.x for a while) Sorry for the troubles... -- Cheers Jorge.-

March 10, 2011

big mistake with hg

by obeythepenguin＠gmail.com

Try 'hg strip': http://mercurial.selenic.com/wiki/Strip Cheers, ~Benjamin On 3/10/11, Jorge Arellano Cid <jcid(a)dillo.org> wrote: > Hi there, > > I just pushed 120 changesets to hg "dillo" instead of "dillo_port1.3" > by mistake (wrong default). > > Is there a simple way to clean the mess by purging the changes? > > > -- > Cheers > Jorge.- > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

March 10, 2011

big mistake with hg

by johannes.hofmann＠gmx.de

On Thu, Mar 10, 2011 at 04:46:32PM +0000, Jorge Arellano Cid wrote: > Hi there, > > I just pushed 120 changesets to hg "dillo" instead of "dillo_port1.3" > by mistake (wrong default). > > Is there a simple way to clean the mess by purging the changes? If it's the last push to the "dillo" repo, you can run hg rollback on the master repo. Alternatively you can do hg clone -r <last good revision> dillo dillo_purged to create a new purged clone and then replace the master repo with that. Cheers, Johannes

March 10, 2011

big mistake with hg

by jcid＠dillo.org

On Thu, Mar 10, 2011 at 01:46:32PM -0300, Jorge Arellano Cid wrote: > Hi there, > > I just pushed 120 changesets to hg "dillo" instead of "dillo_port1.3" > by mistake (wrong default). > > Is there a simple way to clean the mess by purging the changes? BTW, I just also pushed them correctly to "dillo_port1.3", so now there's a new UI and no need to apply any patch on top. This is not finished, I'm working on the details (minor stuff) but decided to commit early so everybody can try the code. The missing parts already work in my prototype so it's more merging work than anything. BTW, tabs are completely new (custom which gives more control over them), and part of a major simplification of the code. For instance I hooked right-click to close-tab just for testing and it feels handy! :) Please enjoy. -- Cheers Jorge.-

March 10, 2011

big mistake with hg

by jcid＠dillo.org

Hi there, I just pushed 120 changesets to hg "dillo" instead of "dillo_port1.3" by mistake (wrong default). Is there a simple way to clean the mess by purging the changes? -- Cheers Jorge.-

March 10, 2011

dillo_port1.3: ctrl-q randomly kills dillo and all tabs

by jcid＠dillo.org

On Thu, Mar 03, 2011 at 04:40:28PM -0900, Roger wrote: > > On Tue, Mar 01, 2011 at 01:02:30PM +0000, corvid wrote: > >Roger wrote: > >> I took a snapshot of dillo_port1.3 a week or so ago and have been finding on > >> CTRL+Q randomly acts like ALT+Q (or kills the Dillo session with all open > >> tabs). > >> > >> One way I've been able to reproduce this, loading several websites and letting > >> them to load completely and then do CTRL+Q. (This bug doesn't present itself > >> on simpler web pages such as google.com or a simple weather forecasting > >> website. Need something with some junk in it. :-/) > > > >How does it behave with more recent code? > > Looks good now. Just pulled a snapshot this morning & built. > > This bug hasn't occurred yet. > > Side note -- the tabs don't refresh as being closed. I'm working on the UI, and decided to implement a new, custom tab mechanism for 1.3 (it is in my HD now). After all the old one had some problems we couldn't fix. When I have it working more or less stable I'll commit. -- Cheers Jorge.-

March 4, 2011

dillo_port1.3: ctrl-q randomly kills dillo and all tabs

by rogerx.oss＠gmail.com

> On Tue, Mar 01, 2011 at 01:02:30PM +0000, corvid wrote: >Roger wrote: >> I took a snapshot of dillo_port1.3 a week or so ago and have been finding on >> CTRL+Q randomly acts like ALT+Q (or kills the Dillo session with all open >> tabs). >> >> One way I've been able to reproduce this, loading several websites and letting >> them to load completely and then do CTRL+Q. (This bug doesn't present itself >> on simpler web pages such as google.com or a simple weather forecasting >> website. Need something with some junk in it. :-/) > >How does it behave with more recent code? Looks good now. Just pulled a snapshot this morning & built. This bug hasn't occurred yet. Side note -- the tabs don't refresh as being closed. -- Roger http://rogerx.freeshell.org/

March 4, 2011

Resizing a window changes the reading location

by Johannes.Hofmann＠gmx.de

On Thu, Mar 03, 2011 at 03:11:59PM -0500, Dennis Nezic wrote: > When windows (with wrapping lines) are resized, the page position > changes, and users have to manually find where they left off. It looks > like a rounding error, since the % in the page is roughly the same -- > but not exactly. I think the absolute offset in pixels - not the percentage is remembered. Simply switching to a percentage based scheme is problematic as the overall height of the page changes while loading.

March 3, 2011

Resizing a window changes the reading location

by dennisn＠dennisn.dyndns.org

When windows (with wrapping lines) are resized, the page position changes, and users have to manually find where they left off. It looks like a rounding error, since the % in the page is roughly the same -- but not exactly.

March 3, 2011

Bug: dillo fails to follow the redirects and reach the webpage

by Johannes.Hofmann＠gmx.de

On Tue, Mar 01, 2011 at 08:14:01AM +0000, Jeremy Henty wrote: > Benjamin Johnson wrote: > > > The default is not to allow automatic requests (such as redirects) > > unless they're from the same domain. Frankly I think this is a > > stupid default, because even though it's a little more secure, it > > also breaks most real world sites. > > I agree. The default even breaks Google. No doubt the security > concerns are real but we need a solution that is not so bad for > usability. Does anyone know if other browsers take similar > precautions, and what their algorithm is? I think the security concern is real - see e.g. here: http://www.owasp.org/index.php/CSRF But I would be happy if someone would come up with some more sophisticated security measures that would allow us be more compatible with common websites by default. Maybe something as described in http://www.owasp.org/index.php/File:RequestRodeo-MartinJohns.pdf Not sure whether this is still state of the art, but it sounds at least reasonable. Cheers, Johannes

March 1, 2011