GNOME Bugzilla – Bug 766474
Don't include default WebKit bookmark
Last modified: 2016-09-17 21:21:01 UTC
Epiphany 3.20.2 on Ubuntu 16.10 (development) Epiphany 3.20.2 added a new default bookmark for WebKit.org. https://git.gnome.org/browse/epiphany/commit/?h=gnome-3-20&id=6fda87aa7b While WebKit.org is useful for web developers, it is not relevant to non-developer users of web browsers. The fact that Epiphany uses WebKit is clearly stated in the About window. I recommend this default bookmark be removed. Consider making the WebKit text in the About window a link instead. That way, people who see WebKit in About and want to learn more about it can do so easily.
(In reply to Jeremy Bicha from comment #0) > Epiphany 3.20.2 on Ubuntu 16.10 (development) > > Epiphany 3.20.2 added a new default bookmark for WebKit.org. > > https://git.gnome.org/browse/epiphany/commit/?h=gnome-3-20&id=6fda87aa7b > > While WebKit.org is useful for web developers, it is not relevant to > non-developer users of web browsers. Same with gnome.org. These were intended to be placeholders users can visit once to learn what technologies the browser is based on, not actually useful bookmarks. I kinda prefer the current a approach, but I guess we could replace these with popular web sites (YouTube, Facebook, etc.) instead; what do you think about that?
I think linking to gnome.org is a good move since the GNOME website is useful to a wide range of Epiphany users. Debian (and therefore Ubuntu too) has had gnome.org in Epiphany's default bookmarks for years! Although links to YouTube and Facebook would be useful (or at least not harmful) to a lot of people, other people don't like those web sites. Therefore, I suggest not adding those links. (These defaults only affect new installs anyway; once Epiphany is run once, changing the default bookmarks has no effect on existing profiles.)
The following fix has been pushed: 430f7d2 Remove WebKit default bookmark
Created attachment 335779 [details] [review] Remove WebKit default bookmark Jeremy complains that it's overly technical, and *grumble* he's probably right. We don't expect users to know what a web browser is, let alone a web rendering engine.