At the ARC meeting today, a few questions were raised. I'm hoping the
project team can provide some clarity on these points:
1) How is WebKit presented to the user? Is it a standalone program that
users can run, or is it only embedded in various GNOME programs that
use it's embedded browsing capabilities, or both? For example, I
believe it is going to be used by the GNOME help browser, yelp, for
navigating help documentation. Could the project team explain in
more detail what uses WebKit and how it presents itself to the end
user?
2) Exactly how does WebKit fail when a user tries to access a HTTPS
website. Since it is not built with HTTPS support, ARC wants to
make sure that it doesn't in any way mislead the user. A user
should not be misled into thinking it is working when it is not.
In other words, it should be clear to the end user that when they try
to visit a HTTPS website with WebKit that it doesn't work. It should
also be usable, so it shouldn't just crash or similar. Does it pop
up a dialog informing the user about the issue?
Or is this a non-issue since it is only being provided for the
purposes of programs like yelp which use its embedded browsing
features?
Thanks,
Brian
