From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mail.oboj.net ([195.178.185.14]) by ewsd; Sun Mar 22 16:43:14 EDT 2020
Received: from localhost (localhost [127.0.0.1])
	by mail.oboj.net (Postfix) with ESMTP id 9381BC0BE6E;
	Sun, 22 Mar 2020 21:43:00 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at mail.oboj.net
Received: from mail.oboj.net ([127.0.0.1])
	by localhost (mail.oboj.net [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id EGE8KhJpSpHk; Sun, 22 Mar 2020 21:43:00 +0100 (CET)
Received: from www.oboj.net (unknown [195.178.185.23])
	by mail.oboj.net (Postfix) with ESMTP id 6FF54C166E1;
	Sun, 22 Mar 2020 21:27:06 +0100 (CET)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Date: Sun, 22 Mar 2020 22:27:06 +0200
From: jamos@oboj.net
To: 9front@9front.org
Subject: Re: [9front] adding javascript enable to netsurf
In-Reply-To: <F561B0E895D7CE19E76C91CC3630E224@hera.eonet.ne.jp>
References: <F561B0E895D7CE19E76C91CC3630E224@hera.eonet.ne.jp>
Message-ID: <3847d6682523c6f2857ab137794bbb27@oboj.net>
X-Sender: jamos@oboj.net
User-Agent: Roundcube Webmail/1.3.4
Content-Transfer-Encoding: quoted-printable
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: polling component polling content-driven-oriented locator 


> It appears on arm nsfb(5.nsfb), but not does on 386 or amd64 nsfb.
> It does not appear when I observe http://www.netsurf-browsers.org/,
> even on 5.nsfb.

Yes, it is a fact that 5.nsfb doesn=E2=80=99t render correctly. Web pages=
 seem=20
functional, but rendering and placement is off. I checked the=20
framebuffer driver using the test cases and they work fine, which isn=E2=80=
=99t=20
too surprising, given that the toolbar looks right.

It might be, as you suggested, something with the CSS handling. The=20
question is: how to debug? If there is a crash, it is possible to make a=20
stack trace. There are unit tests for CSS (and many other functions) but=20
I have not tried to jumpstart them. I have also run the the browser in=20
verbose mode (-v) and compared the output between 386 and arm, but=20
nothing really sticks out for me. I=E2=80=99d be interested in any ideas =
on how=20
to approach debugging this.

Jonas