From: Phil Blundell <pb@pbcl.net>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: RFC: Web browsing and HTML in OE-Core
Date: Thu, 22 Aug 2013 15:18:43 +0100 [thread overview]
Message-ID: <1377181123.13664.11.camel@phil-desktop.brightsign> (raw)
In-Reply-To: <1377180295.6762.19.camel@ted>
On Thu, 2013-08-22 at 15:04 +0100, Richard Purdie wrote:
> With that in mind, I think some kind of HTML support in OE-Core is
> important going forward. Equally, I dislike having things there which we
> cannot test. I know some people have looked into this and it appears
> midori is the best option for something with a small number of
> additional dependencies. I therefore currently think this is something
> we should make a decision to include since it gives us significantly
> better coverage of things like webkit which are a already in the core
> yet totally untested at present.
WebKit itself comes with a bunch of test wrappers (and tests!) for
different platforms and if the aim of the exercise is to test webkit
then it seems like maybe we should just be installing and using those.
Midori would be fine for testing the parts of webkit that it uses, but
obviously it doesn't exercise anything other than the Gtk port which
still leaves you with a bit of a hole in your coverage.
p.
next prev parent reply other threads:[~2013-08-22 14:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 14:04 RFC: Web browsing and HTML in OE-Core Richard Purdie
2013-08-22 14:18 ` Phil Blundell [this message]
2013-08-23 11:17 ` Richard Purdie
2013-08-23 15:56 ` Phil Blundell
2013-08-23 16:14 ` Richard Purdie
2013-08-23 17:03 ` Phil Blundell
2013-08-22 14:24 ` Samuel Stirtzel
2013-08-23 11:16 ` Richard Purdie
2013-08-22 17:24 ` Otavio Salvador
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=1377181123.13664.11.camel@phil-desktop.brightsign \
--to=pb@pbcl.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/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