From: "Philip Silva via 9fans" <9fans@9fans.net>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] netsurf or opossum
Date: Thu, 07 Jan 2021 20:50:10 +0000 [thread overview]
Message-ID: <5rbTmvN4py9HznkO51n46YIUVQx4BU72GnmgUafmmMbqvTyFYdL6C2fn0SLVxfhHpSUErDyOkbfCDIrjyLFYWj7g358XI8XNPmsFspizYUM=@protonmail.com> (raw)
In-Reply-To: <CALAsyW0OK=+dkngaaqURiWSSxgMCBEKw2kfFoj4kA16ZUowjVQ@mail.gmail.com>
To be fair I think the rendering quality can be attributed to the html/css processing. For instance parsing is completely done by golang.org/x/net/html and github.com/aymerick/douceur. (Also one can get quite far with handling display: inline/inline-block/flex and height/width attributes)
One disadvantage might be that some existing HTML styling attributes aren't implemented yet like colspan or "standard" tags like textarea or radio inputs although that's easy to implement. Also it's quite speculative how far one could get with JS which is essentially based on goja and domino. But it's promising that jQuery click handlers work in isolated examples, despite the onclick attribute not even being implemented.
Probably it's also worth mentioning that memory consumption is comparable to that of a regular browser on macOS. Maybe this could be solved by some kind of tree slicing.
In any case I think developing is fun most of the time!
Greetings, Philip
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
Am Donnerstag, 7. Januar 2021 09:28 schrieb Mark van Atten <vanattenmark@gmail.com>:
> http://git.pmikkelsen.com/ph/opossum
>
> -----------------------------------------
>
> 9fans: 9fans
> Permalink: https://9fans.topicbox.com/groups/9fans/T9a725c37f61954a8-Mf2d9006c5749e4decf646828
> Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T9a725c37f61954a8-Mc647b1b9c4ce279c9a88b6a4
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-01-07 20:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 6:52 kokamoto
2021-01-07 8:07 ` Lucio De Re
2021-01-07 8:28 ` Mark van Atten
2021-01-07 20:50 ` Philip Silva via 9fans [this message]
2021-01-07 23:24 ` kokamoto
2021-01-08 5:48 ` kokamoto
2021-04-22 1:34 ` kokamoto
2021-04-22 7:36 ` Philip Silva via 9fans
2021-04-22 7:39 ` Philip Silva via 9fans
2021-04-23 4:37 ` kokamoto
2021-04-23 13:10 ` Philip Silva via 9fans
2021-04-24 0:18 ` kokamoto
2021-04-24 2:00 ` kokamoto
2021-04-24 15:51 ` Philip Silva via 9fans
2021-04-25 4:07 ` kokamoto
2021-04-26 18:25 ` Philip Silva via 9fans
2021-04-26 19:29 ` ori
2021-05-03 20:45 ` Philip Silva via 9fans
2021-05-04 0:56 ` kokamoto
2021-05-04 4:11 ` kokamoto
2021-05-04 4:14 ` kokamoto
2021-05-08 10:12 ` Philip Silva via 9fans
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='5rbTmvN4py9HznkO51n46YIUVQx4BU72GnmgUafmmMbqvTyFYdL6C2fn0SLVxfhHpSUErDyOkbfCDIrjyLFYWj7g358XI8XNPmsFspizYUM=@protonmail.com' \
--to=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).