- Dillo-dev - lists.mailman3.com

Reddit regression

by onepoint＠starurchin.org

Sebastian Geerken wrote: > On Mon, May 05, 2014, Sebastian Geerken wrote: > > On Mo, Mai 05, 2014, Jeremy Henty wrote: > > > > > > Things are progressing nicely (I have already abandoned two problem > > > reports because they were fixed in the meantime) but there has been an > > > unfortunate regression - a few days ago Reddit comment threads started > > > thrashing the CPU. Example: > > > > > > http://www.reddit.com/r/haskell/comments/24rcf0/hourglass_a_new_simpler_tim… > > > > > > This is bad news for me as I follow a lot of subreddits. I hope it > > > can be fixed soon. If there is anything I can do to help find the > > > problem please say so. > > > > Aside from testing, perhaps simplification of pages, see attached > > example, which has all stripped off which is not neccessary to > > reproduce the bug. (It is largely intuition to get there, so perhaps > > it is best when I do this.) > > > > Expect a fix soon. > > Fixed. Marvellous! Regards, Jeremy Henty

May 7, 2014

Reddit regression

by sgeerken＠dillo.org

On Mon, May 05, 2014, Sebastian Geerken wrote: > On Mo, Mai 05, 2014, Jeremy Henty wrote: > > > > Things are progressing nicely (I have already abandoned two problem > > reports because they were fixed in the meantime) but there has been an > > unfortunate regression - a few days ago Reddit comment threads started > > thrashing the CPU. Example: > > > > http://www.reddit.com/r/haskell/comments/24rcf0/hourglass_a_new_simpler_tim… > > > > This is bad news for me as I follow a lot of subreddits. I hope it > > can be fixed soon. If there is anything I can do to help find the > > problem please say so. > > Aside from testing, perhaps simplification of pages, see attached > example, which has all stripped off which is not neccessary to > reproduce the bug. (It is largely intuition to get there, so perhaps > it is best when I do this.) > > Expect a fix soon. Fixed. Interestingly, the fix was in some rather old part of dw; the old implementation did not seem to work properly with extremes (e. g. <button> within <table>), so it is strange that this bug was invisble until now. Sebastian

May 6, 2014

Reddit regression

by sgeerken＠dillo.org

On Mo, Mai 05, 2014, Jeremy Henty wrote: > > Things are progressing nicely (I have already abandoned two problem > reports because they were fixed in the meantime) but there has been an > unfortunate regression - a few days ago Reddit comment threads started > thrashing the CPU. Example: > > http://www.reddit.com/r/haskell/comments/24rcf0/hourglass_a_new_simpler_tim… > > This is bad news for me as I follow a lot of subreddits. I hope it > can be fixed soon. If there is anything I can do to help find the > problem please say so. Aside from testing, perhaps simplification of pages, see attached example, which has all stripped off which is not neccessary to reproduce the bug. (It is largely intuition to get there, so perhaps it is best when I do this.) Expect a fix soon. Sebastian

May 5, 2014

Reddit regression

by onepoint＠starurchin.org

Things are progressing nicely (I have already abandoned two problem reports because they were fixed in the meantime) but there has been an unfortunate regression - a few days ago Reddit comment threads started thrashing the CPU. Example: http://www.reddit.com/r/haskell/comments/24rcf0/hourglass_a_new_simpler_tim… This is bad news for me as I follow a lot of subreddits. I hope it can be fixed soon. If there is anything I can do to help find the problem please say so. Regards, Jeremy Henty

May 5, 2014

character references, trailing ';', urls

by jcid＠dillo.org

On Mon, May 05, 2014 at 02:25:01AM +0000, eocene wrote: > Jorge wrote: > > On Mon, May 05, 2014 at 12:54:06AM +0000, eocene wrote: > > > Jorge wrote: > > > > On Sun, May 04, 2014 at 09:09:48PM +0000, eocene wrote: > > > > > This msg says that it was changed because it wasn't required under > > > > > certain conditions. HTML4 spec gives it as: > > > > > > > > > > Note. In SGML, it is possible to eliminate the final ";" after a > > > > > character reference in some cases (e.g., at a line break or > > > > > immediately before a tag). In other circumstances it may not be > > > > > eliminated (e.g., in the middle of a word). We strongly suggest > > > > > using the ";" in all cases to avoid problems with user agents that > > > > > require this character to be present. > > > > > > > > > > > > > > > ...and there's an "IIRC" in the msg that XHTML requires it. > > > > > > > > > > The HTML5 spec requires a terminating ';' in all cases. > > > > > > > > Then, it looks like requiring it again in this case may be > > > > the way to go (I seem to recall there were lots of unterminated NBSP). > > > > > > Are you saying always for html5, (probably) always for xhtml, and for > > > attributes with html4? > > > > I'm saying we should find a simple heuristic that copes with > > the current situation. > > If you want simple, I can just require it unconditionally and > find out what happens. Your first suggestion looks quite reasonable. Please try it and make some field tests. I'm currently working on the double imgbuf problem... -- Cheers Jorge.-

May 5, 2014

character references, trailing ';', urls

by eocene＠gmx.com

Jorge wrote: > On Mon, May 05, 2014 at 12:54:06AM +0000, eocene wrote: > > Jorge wrote: > > > On Sun, May 04, 2014 at 09:09:48PM +0000, eocene wrote: > > > > This msg says that it was changed because it wasn't required under > > > > certain conditions. HTML4 spec gives it as: > > > > > > > > Note. In SGML, it is possible to eliminate the final ";" after a > > > > character reference in some cases (e.g., at a line break or > > > > immediately before a tag). In other circumstances it may not be > > > > eliminated (e.g., in the middle of a word). We strongly suggest > > > > using the ";" in all cases to avoid problems with user agents that > > > > require this character to be present. > > > > > > > > > > > > ...and there's an "IIRC" in the msg that XHTML requires it. > > > > > > > > The HTML5 spec requires a terminating ';' in all cases. > > > > > > Then, it looks like requiring it again in this case may be > > > the way to go (I seem to recall there were lots of unterminated NBSP). > > > > Are you saying always for html5, (probably) always for xhtml, and for > > attributes with html4? > > I'm saying we should find a simple heuristic that copes with > the current situation. If you want simple, I can just require it unconditionally and find out what happens. > > > A long long time ago people thought that SGML was the final > > > solution, then XML, then HTML5, now they're looking for an > > > alternative technology to base the web upon... > > > > Where have they been talking about an alternative technology? > > I remember short ago, reading somewhere in the news that there > were funds and a call for people with expertise to work on > designing an alternative technology for the web (to try to tackle > the enormous amount of complexity full blown browsers have become > not to mention the disparate user experience this creates). I wish them luck. HTML5 is the most ridiculous possible document.

May 5, 2014

character references, trailing ';', urls

by jcid＠dillo.org

On Mon, May 05, 2014 at 12:54:06AM +0000, eocene wrote: > Jorge wrote: > > On Sun, May 04, 2014 at 09:09:48PM +0000, eocene wrote: > > > This msg says that it was changed because it wasn't required under > > > certain conditions. HTML4 spec gives it as: > > > > > > Note. In SGML, it is possible to eliminate the final ";" after a > > > character reference in some cases (e.g., at a line break or > > > immediately before a tag). In other circumstances it may not be > > > eliminated (e.g., in the middle of a word). We strongly suggest > > > using the ";" in all cases to avoid problems with user agents that > > > require this character to be present. > > > > > > > > > ...and there's an "IIRC" in the msg that XHTML requires it. > > > > > > The HTML5 spec requires a terminating ';' in all cases. > > > > Then, it looks like requiring it again in this case may be > > the way to go (I seem to recall there were lots of unterminated NBSP). > > Are you saying always for html5, (probably) always for xhtml, and for > attributes with html4? I'm saying we should find a simple heuristic that copes with the current situation. > > > A long long time ago people thought that SGML was the final > > solution, then XML, then HTML5, now they're looking for an > > alternative technology to base the web upon... > > Where have they been talking about an alternative technology? I remember short ago, reading somewhere in the news that there were funds and a call for people with expertise to work on designing an alternative technology for the web (to try to tackle the enormous amount of complexity full blown browsers have become not to mention the disparate user experience this creates). -- Cheers Jorge.-

May 5, 2014

character references, trailing ';', urls

by eocene＠gmx.com

Jorge wrote: > On Sun, May 04, 2014 at 09:09:48PM +0000, eocene wrote: > > This msg says that it was changed because it wasn't required under > > certain conditions. HTML4 spec gives it as: > > > > Note. In SGML, it is possible to eliminate the final ";" after a > > character reference in some cases (e.g., at a line break or > > immediately before a tag). In other circumstances it may not be > > eliminated (e.g., in the middle of a word). We strongly suggest > > using the ";" in all cases to avoid problems with user agents that > > require this character to be present. > > > > > > ...and there's an "IIRC" in the msg that XHTML requires it. > > > > The HTML5 spec requires a terminating ';' in all cases. > > Then, it looks like requiring it again in this case may be > the way to go (I seem to recall there were lots of unterminated NBSP). Are you saying always for html5, (probably) always for xhtml, and for attributes with html4? > A long long time ago people thought that SGML was the final > solution, then XML, then HTML5, now they're looking for an > alternative technology to base the web upon... Where have they been talking about an alternative technology?

May 5, 2014

character references, trailing ';', urls

by jcid＠dillo.org

On Sun, May 04, 2014 at 09:09:48PM +0000, eocene wrote: > I wrote: > > Jorge wrote: > > > AFAIR the original routine was written to require the trailing ';' > > > and it worked well for some time. Then more pages started to show > > > unterminated entities inside, and it got so annoying we decided to > > > make it more flexible and not to require the ';' when the entity > > > name was found (IIRC). > > > > Yeah, this is why I was considering just changing the get_attr case, > > but of course I don't want to make the code messy and complicated > > unless I need to. > > > > > It'd be good to find the reason for the change before reverting it. > > > I don't remember it now, but I do remember it was because the other way > > > started to be perceived as worst in some sense. > > > > > > Maybe GMANE has the mailing list archives... > > > > I guess I'll put some time into digging around. > > http://lists.dillo.org/pipermail/dillo-dev/2005-January/002502.html > > where we get the end of a conversation between Jorge and Matthias Franz. > > This msg says that it was changed because it wasn't required under > certain conditions. HTML4 spec gives it as: > > Note. In SGML, it is possible to eliminate the final ";" after a > character reference in some cases (e.g., at a line break or > immediately before a tag). In other circumstances it may not be > eliminated (e.g., in the middle of a word). We strongly suggest > using the ";" in all cases to avoid problems with user agents that > require this character to be present. > > > ...and there's an "IIRC" in the msg that XHTML requires it. > > The HTML5 spec requires a terminating ';' in all cases. Then, it looks like requiring it again in this case may be the way to go (I seem to recall there were lots of unterminated NBSP). A long long time ago people thought that SGML was the final solution, then XML, then HTML5, now they're looking for an alternative technology to base the web upon... -- Cheers Jorge.-

May 5, 2014

character references, trailing ';', urls

by eocene＠gmx.com

I wrote: > Jorge wrote: > > AFAIR the original routine was written to require the trailing ';' > > and it worked well for some time. Then more pages started to show > > unterminated entities inside, and it got so annoying we decided to > > make it more flexible and not to require the ';' when the entity > > name was found (IIRC). > > Yeah, this is why I was considering just changing the get_attr case, > but of course I don't want to make the code messy and complicated > unless I need to. > > > It'd be good to find the reason for the change before reverting it. > > I don't remember it now, but I do remember it was because the other way > > started to be perceived as worst in some sense. > > > > Maybe GMANE has the mailing list archives... > > I guess I'll put some time into digging around. http://lists.dillo.org/pipermail/dillo-dev/2005-January/002502.html where we get the end of a conversation between Jorge and Matthias Franz. This msg says that it was changed because it wasn't required under certain conditions. HTML4 spec gives it as: Note. In SGML, it is possible to eliminate the final ";" after a character reference in some cases (e.g., at a line break or immediately before a tag). In other circumstances it may not be eliminated (e.g., in the middle of a word). We strongly suggest using the ";" in all cases to avoid problems with user agents that require this character to be present. ...and there's an "IIRC" in the msg that XHTML requires it. The HTML5 spec requires a terminating ';' in all cases.

May 4, 2014