GNOME Web

GNOME Web was originally named "Epiphany", but was rebranded in 2012 as part of GNOME 3.4.[14] The name Epiphany is still used internally, as its code name,[8] for development and in the source code.[15] The package remains epiphany-browser in Debian[16] (to avoid a name collision with a video game that is also called "Epiphany") and epiphany in Fedora and Arch Linux.[17][18]

Marco Pesenti Gritti, the initiator of Galeon, originally developed Epiphany in 2002 as a fork of Galeon. The fork occurred because of the disagreement between Gritti and the rest of Galeon developers about new features. While Gritti regarded Galeon's monolithic design and the number of user-configurable features as factors limiting Galeon's maintainability and usability, the rest of the Galeon developers wanted to add more features.

Around the same time, the GNOME project adopted a set of human interface guidelines, which promoted simplification of user interfaces. As Galeon was oriented towards power users, most developers disapproved. As a result, Gritti created a new browser based on Galeon, with most of the non-critical features removed. He intended Epiphany to comply with the GNOME HIG. As such, Epiphany used the global GNOME theme and other settings from inception.[19][20]

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.

[..]

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[21]

Galeon continued after the fork, but lost momentum due to the remaining developers' failure to keep up with changes in the Mozilla platform. Galeon development stalled and the developers decided to work on extensions to bring Galeon's advanced features to Epiphany.[20]

Gritti ended his work on Epiphany and a GNOME team led by Xan Lopez, Christian Persch and Jean-François Rameau now direct the project.[22] Gritti died of cancer on May 23, 2015.[23]

The first version of Epiphany was released on December 24, 2002.[2]

Epiphany initially used the Gecko layout engine from the Mozilla project to display web pages. It provided a GNOME graphical user interface for Gecko, instead of Mozilla's cross-platform interface.[24]

The development of Epiphany was mainly focused on usability improvements compared to major browsers at the time. The most notable was the new text entry widget, which was introduced in version 1.8. The new widget supported icons inside the text area and reduced the screen space needed to present information, while improving GNOME integration.[25]

The next major milestone was version 2.14, which was the first to follow GNOME's version numbering. It also featured network awareness using NetworkManager, smart bookmarks improvements, and the option to build with XULRunner.

The latter was critical. Previously, Epiphany could only use an installed Mozilla web browser as a web engine provider. The XULRunner support made it possible to install Epiphany as the only web browser on the system.[26][27]

Web Inspector, showing a Safari-like user interface

The development process suffered from major problems related to the Gecko backend. Notably, the release cycles of the two projects did not line up efficiently. Also, Mozilla increasingly disregarded third-party software that wished to make use of Gecko, until it became viewed as an integrated Firefox component.[22] To address these issues, in July 2007, the Epiphany team added support for WebKit as an alternative rendering engine.[28] On April 1, 2008, the team announced that it would remove the ability to build it using Gecko and proceed using only WebKit.[22]

The size of the team and complexity of porting the browser to WebKit caused version 2.22 to be re-released with bugfixes alongside GNOME 2.24,[29] so the releases stagnated until July 1, 2009, when it was announced that 2.26 would be the final Gecko-based version.[30]

In September 2009, the transition to WebKit was completed as part of GNOME 2.28.[31]

Developers of GNOME Web maintain a complete and accurate changelog in its official repository that shows complete and detailed changes between all the releases,[32] following table just shows arbitrarily mentioned some notable and important changes:[33][34]

The underlying WebKit browser engine provides support for HTML 4, XHTML, CSS 1 and 2, most of HTML 5 and CSS 3,[84] and a Web Inspector (web development debugging tool).[58]

Encrypted Media Extensions support is not a goal, as the standard does not specify a Content Decryption Module to use, all available modules are proprietary even if licensing is possible, and the system imposes Digital Rights Management that hides what the user's computer is doing to make copying "premium content" difficult. However, Media Source Extensions is supported, as YouTube began to require this technology in November 2018.[85]

Apple, which is the primary corporate backer of WebKit, rejected at least 16 web APIs because they could be used in a fingerprinting attack to help personally identify users and track them, while providing limited or no benefit to the user.[86] As HTML5test checks for most of these APIs, it artificially lowers WebKit's "score" in points (as does lack of DRM support).

Web once supported NPAPI plug-ins, such as Java and Adobe Flash, but support was removed in GNOME 3.34.[75] In the modern web platform, these have fallen out of favor and support has been removed from all major browsers. Flash has been deprecated by Adobe itself.[87] Flash had gained infamy throughout the years for usability and stability issues, incessant security vulnerabilities,[88] its proprietary nature, its ability to let sites deploy particularly obnoxious web ads,[89] and Adobe's poor and inconsistent Linux support.[90] Many of these issues were raised by Steve Jobs, then CEO of Apple, in his essay Thoughts on Flash.[91]

Support for phone and tablet form-factors was added in version 3.34

Web reuses GNOME frameworks and settings,[92][93] including the user interface theme, network settings, and printing. Settings are stored with GSettings and GNOME default applications are used for internet media types handling. The user configures these, centrally, in GNOME's settings app.

The built-in preference manager for Web presents basic browser-specific settings while advanced settings which could radically alter Web's behavior can be changed with utilities such as dconf (command line) and dconf-editor (graphical).[94]

Web follows the GNOME Human Interface Guidelines and platform-wide design decisions.[95] For example, in Web 3.4, the menu for application actions was moved to the GNOME Shell's top panel application menu and the menu bar was replaced with "super menu" button, which triggers the display of window-specific menu entries.[96]

Since GNOME 3.32, Web can adjust to various form factors with the help of libhandy, a library sponsored by Purism.[97] It supports desktop, tablet and phone form factors. ("Narrow Mode").[98]

Since GNOME 3.18, Web is configured to block ads and pop-ups by default.[72] In GNOME 3.34, the existing ad blocker was removed. This code was only partially functional and had been the source of many bugs. Web adopted the "Content Blockers" system from the WebKit engine.[99][100]

One of the developers, Adrián Pérez de Castro, compared the old and new ad blockers. He found that the switch saved approximately 80 MiB of RAM per browser tab.[101]

Since GNOME 3.28, Web has support for Google Safe Browsing, to help prevent users from visiting malicious websites.[82]

Since GNOME 3.34, Web explicitly requires a minimum of WebKitGTK 2.26 or later.[74][102][75] This provides the "Bubblewrap Sandbox"[103] for tab processes, which is intended to prevent malicious websites from hijacking the browser and using it to spy on other tabs or run malicious code on the user's computer. If such code found another exploit in the operating system allowing it to become root, the result could be a disaster for all users of the system.

Making the sandbox a priority was brought on, according to Michael Catanzaro, because he was particularly concerned with the code quality of OpenJPEG and the numerous security problems that had been discovered in it, including many years of failing security reviews by Ubuntu.[104] He further explained that web compatibility requires that sites believe that Web is a major browser. Sending them the user agent of Apple Safari causes fewer broken websites than others (due to sharing the WebKit engine), but also causes caching servers to deliver JPEG 2000 images,[105] of which Safari is the only major browser to support. There is no other usable open source option for JPEG 2000 support. Fixing OpenJPEG, which is the official reference software, will be a massive undertaking that could take years to sort out. Enabling the Bubblewrap Sandbox would cause many vulnerabilities in this and other components to become "minimally useful" to potential attackers.[106]

In GNOME 3.36, Web gained native support for PDF documents by using PDF.js. Michael Catanzaro explained that having websites open Evince to display PDF files was insecure, as it could be used to escape the browser's security sandbox. Since Evince was the last user of NPAPI, this allowed the remaining support code for the obsolete plug-in model (where additional vulnerabilities could be hiding) to be removed. Since the NPAPI support had a hard dependency on X11, moving to PDF.js also allowed that dependency to be dropped.[77]

Since PDF.js internally converts PDF documents so that they can be displayed by the web browser's engine, it does not add security vulnerabilities to the browser the way that compiled plug-ins such as Adobe Acrobat or Evince could.[77]

Bookmark management of GNOME Web in version 41

While most browsers feature a hierarchical folder-based bookmark system, Web uses categorized bookmarks, where a single bookmark (e.g. this page) can exist in multiple categories (such as "Web Browsers", "GNOME", and "Computer Software").[107] A special category includes bookmarks that have not yet been categorized. Bookmarks, along with browsing history, are accessed from the address bar in find-as-you-type manner.[108]

Another innovative concept supported by Web (though originally from Galeon)[19] is "smart bookmarks". These take a single argument specified from the address bar, or from a textbox in a toolbar.[20]

GNOME Web 3.36 (March 2020) in "Web Application mode", showing the Wikipedia main page

Since GNOME 3.2, released in September 2011,[109] Web allows creating application launchers for web applications. The subsequent invocation of a launcher brings up a plain site-specific browser (single instance) of Web limited to one domain, with off-site links opening in a normal browser.[110] 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.[111] This feature facilitates the integration of the desktop and World Wide Web, which is a goal of Web's developers.[112] 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.[113]

Web applications are managed within the browser'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 while a centralized GNOME web application management was to be implemented in GNOME 3.4, but this never happened.[34]

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.[114]

Web once supported extensions and a package was maintained containing the official ones. This was later removed due to problems with stability and maintainability.

Some popular extensions, such as ad blocking, were moved to the core application.

The project has expressed an interest in implementing support for the WebExtension add-on format used by Chrome, Firefox, and some other major browsers, if interested contributors can be found.[115] Experimental support for WebExtensions was introduced in GNOME 43.[116]