|Original author(s)||Marco Pesenti Gritti|
|Developer(s)||The GNOME Project (mostly by Michael Catanzaro from Igalia)|
|Initial release||24 December 2002|
|Stable release||3.26.0 (13 September 2017) [±]|
|Preview release||3.27.4 (10 January 2018[±])|
|Written in||C (GTK)|
|Operating system||Linux, unix-like|
|Engine||WebKitGTK+ (previously Gecko)|
|Available in||More than 60 languages|
The browser was forked from Galeon, after developers' disagreements about Galeon's growing complexity. Since then Web has been developed as part of the GNOME project and uses most of GNOME's technology and settings when applicable. It is part of the GNOME Core Applications. As required by the GNOME Human Interface Guidelines (HIG), Web maintains a clean and simple graphical user interface with only a required minimum number of features exposed to users by default. The browser's functionality and configurability can be extended with official and third-party extensions.
Instead of developing a custom web browser engine Epiphany originally used the Gecko layout engine until version 2.28 and WebKitGTK+ starting with version 2.20[vague]. This approach allows the relatively small developer community to maintain a sufficient level of modern web standards support. The features of Web include reuse of GNOME configuration settings, smart bookmarks and web application integration into user desktop.
GNOME Web is default web browser on elementary OS and its source code is available under the GNU General Public License. The binary builds of the browser are available in the software repository of most Linux distributions and BSD releases.
Marco Pesenti Gritti, the initiator of Galeon, originally developed Epiphany in 2002 as a fork of Galeon. The fork occurred because of the divergent aims of Gritti and the rest of Galeon development team about new features. While Gritti regarded Galeon's monolithic design and the number of user-configurable features as factors limiting Galeon's maintainability and user base expansion, the rest of the Galeon developers wanted to see more features added. At the same time the GNOME project created the GNOME human interface guidelines, which promoted simplification of user interfaces. As Galeon was oriented towards power users, most developers saw the implementation of those guidelines as unacceptable. As a result, Gritti created a new browser based on Galeon's codebase, with most of the non-mission-critical features removed. He intended Epiphany to comply fully with the GNOME human interface guidelines, with a very simple user-interface. As such, Epiphany does not have its own theme settings and uses GNOME's settings, which are specified in the GNOME Control Center.
Gritti explained his motivations:
While Mozilla has an excellent rendering engine, its default XUL-based interface is considered to be overcrowded and bloated. Furthermore, on slower processors even trivial tasks such as pulling down a menu is less than responsive. Epiphany aims to utilize the simplest interface possible for a browser. Keep in mind that simple does not necessarily mean less powerful. We believe the commonly used browsers of today are too big, buggy, and bloated. Epiphany addresses simplicity with a small browser designed for the web—not mail, newsgroups, file management, instant messaging or coffee making. The Unix philosophy is to design small tools that do one thing, and do it well.— Marco Pesenti Gritti
Galeon continued after the fork, but lost its momentum due to the remaining developers' failure to keep up with the new features and changes Mozilla introduced. Galeon development finally stalled and the developers decided to work on a set of extensions to bring Galeon's advanced features to Epiphany instead.
Epiphany's early philosophy included a commitment to creating a web browser specifically for GNOME:
Epiphany's main goal is to be integrated with the gnome desktop. We don't aim to make Epiphany usable outside Gnome. If someone will like to use it anyway, it's just a plus. For example: Making people happy that don't have control center installed is not a good reason to have mime configuration in Epiphany itself.— Marco Pesenti Gritti
While some promote Epiphany as the default web browser in Linux distributions with GNOME as the default desktop environment, most distros offer Firefox instead. In most minimalist distributions, Epiphany is installed with the GNOME meta-package or packages group.
The first version of Epiphany was released on December 24, 2002.
Epiphany initially used the Gecko layout engine from the Mozilla project to display web pages. It provided a GNOME integrated graphical user interface for Gecko, instead of the Mozilla XUL interface.
The development process of Epiphany was mainly focused on numerous small usability improvements. The most notable of them was the new text entry widget, which first appeared in 1.8 stable version series. The new widget supported icons inside the text area reduced the amount of screen space needed to present the information and improved GNOME integration.
The second major milestone (after version 1.0) in Epiphany development was the 2.14 release. This was the first Epiphany release which followed GNOME's version numbering. It also featured network awareness using NetworkManager, smart bookmarks-related improvements and the possibility of being compiled against XULRunner. The latter was critical, as previously Epiphany could only use Firefox or Mozilla/SeaMonkey as a layout engine provider, so it could only be installed alongside one of those browsers. The XULRunner support made it possible to install Epiphany as the sole web browser on the system.
The development process heavily suffered from multiple problems, related to the Gecko backend. To address these issues in July 2007 the Epiphany team added support for WebKit as an alternative rendering engine for Epiphany. As the backend development advanced, on April 1, 2008 the Epiphany team announced that it would stop using the Gecko rendering engine and proceed using just WebKit.
The size of the development team and the complexity of porting the whole browser to a new backend caused Epiphany to re-release version 2.22 with bugfixes instead of the actual development code, so browser development remained stagnant until July 1, 2009, when the project team announced that Epiphany 2.26 would be the final Gecko-based version. Eventually, in September 2009 the Webkit-powered Epiphany 2.28 was released, as part of GNOME 2.28.
With GNOME 3.4 release Epiphany was renamed to Web. However, the name Epiphany is still used internally for development, such as for bug tracking and in the source code. The package remains epiphany-browser.
|0.4||December 25, 2002||Initial release|
|0.5||April 13, 2003||Ability to drag bookmarks, smart bookmarks and topics to the toolbar, optional Go button for URL bar, "Help" support.|
|0.6||May 4, 2003||Drag and drop of links to tab bar, security preferences, user primary language automatic detection, new history dialog, default bookmarks toolbar.|
|0.7||June 7, 2003||Zoom control for the toolbar, ability to reload page bypassing cache, traditional bookmarks menu, Exit fullscreen button.|
|0.8||July 13, 2003||Tooltips, improved GNOME integration, fast search for bookmarks and history, drag and drop of URLs in the bookmarks toolbar.|
|0.9||August 22, 2003||Bugfixes only.|
|1.0||September 8, 2003
|Support for Mozilla 1.6.|
|1.2||March 15, 2004
|Support for Mozilla 1.7 and 1.8, Lockdown mode, caret navigation.|
|1.4||September 13, 2004
|Offline mode, per site pop-up blocking.|
|1.6||March 9, 2005
|1.8||September 5, 2005
|Python bindings, Find toolbar, Favicon and SSL icons displayed in location bar, Gecko 1.8 support, error messages display in content area, use of the standard GNOME printing system.|
|2.14||March 12, 2006||XULRunner backend supported, topic suggestions in bookmarks manager, version numbering synced to GNOME, NetworkManager DBUS interface support.|
|2.16||September 6, 2006||History preserved for links, opened in new tabs, spell checking support, page security info dialogue from Certificates extension, new GTK+ Printing dialogs, stability improvements.|
|2.18||March 14, 2007||Bookmarks online storage, UI for Ad Blocker.|
|2.20||September 19, 2007||Migration from Gecko to WebKit, PDF printing, migration from gnome-vfs to GIO.|
|2.22||March 12, 2008|
|2.24||September 24, 2008|
|2.26||March 31, 2009|
|2.28||September 24, 2009||Gecko backends removed, Python support for extensions dropped, support for the WebInspector.|
|2.30||March 31, 2010||Broken SSL certificate warning, custom page menus support.|
|2.32||September 29, 2010||Bugfixes only.|
|3.0||April 6, 2011||Reduced the amount of user interface chrome, geolocation support, switched from text zooming to full content zooming, new download manager, migration to GTK+ 3 and GNOME 3 technologies.|
|3.2||September 28, 2011||Separate font settings, WebKit's internal page source viewer made default, Web Applications mode introduced.|
|3.4||March 28, 2012||Renamed from Epiphany to Web, major interface overhaul, performance improvements, super menu introduced.|
|3.6||September 26, 2012||Overview screen and Full Screen mode introduced.|
|3.10||September 26, 2013||New toolbar placement into "Header Bar", the new GNOME titlebar design.|
|3.12||March 25, 2014||A major update version, including improved performance and user interface enhancements. Implemented a single process for each tab.|
|3.14||September 24, 2014||A minor update adding support blocking invalid SSL certificates, warning users about mixed content for improved security, adblocker performance improvements and overall small UI improvements and polishing.|
|3.16||March 23, 2015||UI updated, fixes to improve incognito mode's privacy and discoverability.|
|3.18||September 23, 2015||UI improvements, enabled Do Not Track and the ad blocker by default.|
|3.20||March 23, 2016||UI improvements, Session restore.|
|3.22||September 21, 2016||UI improvements.|
Web reuses GNOME frameworks and settings. Therefore, its user interface theme is the GNOME default theme, the network settings with GNOME NetworkManager configuration, printing with the GNOME printing system, settings with GSettings and GNOME default applications settings are used for internet media types handling.
The built-in preference manager for Web is designed to present user only basic browser-specific settings. All the advanced configuration is done with the stand-alone GSettings configurator tools such as GNOME's default dconf (command line) and dconf-editor (graphical).
Web follows the GNOME Human Interface Guidelines and follows the platform-wide design changes. For example, in Web 3.4 release the menu for application-wide actions was moved to the GNOME Shell's top panel application menu and the menubar was replaced with "super menu" button, which triggers the display of window-specific menu entries.
While most browsers feature a hierarchical folder-based bookmark system, Web uses categorized bookmarks, where a single bookmark (such as "Web") can exist in multiple categories (such as "Web Browsers", "GNOME", and "Computer Software"). A special category includes bookmarks that have not yet been categorized. Another innovative concept supported by Web (though originally from Galeon) is "smart bookmarks". These take a single argument specified from the address bar, or from a textbox in a toolbar. Bookmarks, along with browsing history, are accessed from the address bar in find-as-you-type manner.
Up until version 3.6, Web was extensible with a plugin system called Web extensions. This package was distributed by the developers of Web and contained the official extensions. For version 3.8, this system was removed because of problems with stability and maintainability, with some popular extensions, such as ad blocking, being moved to the core application instead.
Since GNOME 3.2 Web allows creating application launchers for web applications. The subsequent invocation of a launcher brings up a plain single instance of Web limited to one domain, with off-site links opening in a normal browser. The launcher created this way is accessible from the desktop and is not limited to GNOME Shell. For instance it may be used with Unity, used on Ubuntu. This feature facilitates the integration of the desktop and World Wide Web, which is a goal of Web's developers. Similar features can be found in the Windows version of Google Chrome. For the same purpose Mozilla Foundation previously developed a standalone application Mozilla Prism, which was superseded by the project Chromeless.
Web applications are managed within Epiphany's main instance. The applications can be deleted from the page, accessible with a special URI about:applications. This approach was supposed to be a temporary solution and a common GNOME-wide application management was intended to be implemented in GNOME 3.4, but was not rolled out.
Since GNOME 3.26, Web has support for Firefox Sync, which allows users to sync their bookmarks, history, passwords, and open tabs with Firefox Sync, which can then be shared between any copy of Firefox or Web that the user signs into Firefox Sync with.
Being a component of GNOME desktop environment, Web has neither software, nor hardware dependencies beyond the GNOME platform. Though the GNOME Project does not list the minimum system requirements, it states that GNOME 3 should run on any modern computer.
Web is only released as source code or with Linux distributions and BSDs making binary packages. Thus the availability of Web depends on the distributor. Web can be run on many hardware platforms, including i386, amd64 and several other instruction set architectures.
In reviewing the WebKit-powered Epiphany 2.28 in September 2009, Ryan Paul of Ars Technica said "Epiphany is quite snappy in GNOME 2.28 and scores 100/100 on the Acid3 test. Using WebKit will help differentiate Epiphany from Firefox, which is shipped as the default browser by most of the major Linux distributors."
In March 2011 Veronica Henry reviewed Epiphany 2.32, saying "To be fair, this would be a hard sell as a primary desktop browser for most users. In fact, there isn't even a setting to let you designate it as your default browser. But for those instance where you need to fire up a lighting-fast browser for quick surfing, Epiphany will do the trick." She further noted, "Though I still use Firefox as my primary browser, lately it seems to run at a snail's pace. So, one of the first things I noticed about Epiphany is how quickly it launches. And subsequent page loads on my system are equally as fast." Henry criticized Epiphany for its short list of extensions, singling out the lack of Firebug as a deficiency. Web instead supports Web Inspector offered by the WebKit engine, which has similar functionality.
In April 2012 Ryan Paul of Ars Technica used Web as an example to his criticism of GNOME 3.4 design decisions: "Aside from the poor initial discoverability of the panel menu, this model works reasonably well for simple applications. [...] Unfortunately, it doesn't scale well in complex applications. The best example of where this approach can pose difficulties is in GNOME's default Web browser. [...] Having the application's functionality split across two completely separate menus does not constitute a usability improvement." This was addressed in later versions, with a single unified menu.
In an October 2016 review Bertel King Jr. noted on MakeUseOf, "Later versions offer the best integration you will find with GNOME Shell. It lacks the add-ons found in mainstream browsers, but some users will like the minimalism, the speed, and the tab isolation that prevents one misbehaving site from crashing the entire browser."
|Wikimedia Commons has media related to GNOME Web.|
None of the audio/visual content is hosted on this site. All media is embedded from other sites such as GoogleVideo, Wikipedia, YouTube etc. Therefore, this site has no control over the copyright issues of the streaming media.
All issues concerning copyright violations should be aimed at the sites hosting the material. This site does not host any of the streaming media and the owner has not uploaded any of the material to the video hosting servers. Anyone can find the same content on Google Video or YouTube by themselves.
The owner of this site cannot know which documentaries are in public domain, which has been uploaded to e.g. YouTube by the owner and which has been uploaded without permission. The copyright owner must contact the source if he wants his material off the Internet completely.