[go: up one dir, main page]
Wikipedia

Chromium (web browser)

(Redirected from QtWebEngine)
For other uses, see Chromium (disambiguation).

Chromium is a free and open-source web browser project, primarily developed and maintained by Google.[3] It is a widely-used codebase, providing the vast majority of code for Google Chrome and many other browsers, including Microsoft Edge, Samsung Internet, and Opera. The code is also used by several app frameworks.

Chromium
Original author(s)Google[1]
Developer(s)The Chromium Projects,[2] controlled by Google[3]
Initial release2 September 2008; 16 years ago (2008-09-02)[1]
Repository
Written inC++ primarily,[4] HTML, CSS, JavaScript for UI and test suite[5][6]
EnginesV8, Blink (WebKit on iOS/iPadOS)[7]
Operating system
PlatformIA-32, x86-64, ARM, ARM64
LicenseBSD-3[8] and others[9]
Websitewww.chromium.org/Home

Licensing

edit

Chromium is a free and open-source software project. The Google-authored portion is shared under the 3-clause BSD license.[8] Third party dependencies are subject to a variety of licenses, including MIT, LGPL, Ms-PL, and an MPL/GPL/LGPL tri-license.[9]

This licensing permits any party to build the codebase and share the resulting browser executable with the Chromium name and logo. Thus many Linux distributions do this, as well as FreeBSD and OpenBSD.[10]

Differences from Google Chrome

edit

Chromium provides the vast majority of source code for Google Chrome, but there are important differences.

Features

edit

Chromium lacks the following Chrome features:[10]

Branding and licensing

edit

Google first chose the name "Chrome" for its browser.[12][13] Then the open-source release was named "Chromium" because chromium metal is used to make chrome plating.[1]

Chrome has the same user interface functionality as Chromium, but with a Google-branded color scheme. Unlike Chromium, Chrome is not open-source; its binaries are licensed as freeware under the Google Chrome Terms of Service.[14]

Development

edit

The Chromium browser codebase contains over 32 million source lines of code, excluding comments and blank lines.[4]

Contributors

edit

Chromium has been a Google project since its inception,[1][3] and Google employees have done the bulk of the development work.[15]

Google refers to this project and the offshoot ChromiumOS as "the Chromium projects",[2] and its employees use @chromium.org email addresses for this development work. However, in terms of governance, the Chromium projects are not independent entities; Google retains firm control of them.[3]

The Chromium browser codebase is widely used, so others have made important contributions, most notably Microsoft, Igalia, Yandex, Intel, Samsung, LG, Opera, Vivaldi, and Brave.[15][3] Some employees of these companies also have @chromium.org email addresses.

Architecture

edit

Google designed the first multi-process browser.[16][17] Compared to single-process designs, this architecture has better responsiveness with many browser tabs open and security benefits of process isolation, but with the trade-off of higher memory usage.[18][19] This was later refined as per-process website isolation, providing additional security.[18]

Another important design decision was for the browser's user interface to be minimalistic.[17][20][21]

The browser engine was originally based on Apple's WebKit, which Google deemed the "obvious choice" of available options.[22] However, Google's novel multi-process design required engine changes. This divergence from Apple's version increased over time, so in 2013 Google officially forked its version as the Blink engine.[22][23]

Programming languages

edit

C++ is the primary language, comprising over half of the codebase.[4] This includes the Blink and V8 engines, the implementation of HTTP and other protocols, the internal caching system, the extension API, and most of the user interface.[24]

The rest of the user interface, called the WebUI, is implemented in HTML, CSS, and JavaScript (usually via TypeScript transpilation).[24][5] An extensive collection of web platform tests is also written in these languages plus XML.[6][4]

Third-party libraries that provide essential functionality,[25] such as SQLite and numerous codecs, are written in C, C++, or beginning in 2023,[26][27] the newer Rust language.[4]

Support for mobile operating systems requires special languages: for Android both Java and Kotlin, and for iOS both Objective-C and Swift.[5][4]

Python is the main language of the build system,[4] which also has special configuration files for Google's GN tool.[28]

Logistics

edit

The bug tracking system is a publicly accessible website.[29] Participants are identified by their email addresses.

The Chromium continuous integration system automatically builds and tests the codebase several times a day.[30]

Builds are identified by a four-part version number that is major.minor.build.patch.[31] This versioning scheme and the branch points that occur every six to seven weeks are from Google Chrome and its development cycle.[32]

History

edit

2008 to 2010

edit

Google Chrome debuted in September 2008, and along with its release, the Chromium source code was also made available, allowing builds to be constructed from it.[1][33][34]

Upon release, Chrome was criticized for storing a user's passwords without the protection of a master password. Google has insisted that a master password provides no real security against knowledgeable hackers, but users argued that it would protect against co-workers or family members borrowing a computer and being able to view stored passwords as plaintext.[35] In December 2009, Chromium developer P. Kasting stated: "A master password was issue 1397. That issue is closed. We will not implement a master password. Not now, not ever. Arguing for it won't make it happen. 'A bunch of people would like it' won't make it happen. Our design decisions are not democratic. You cannot always have what you want."[36]

 
An alpha build of Chromium 3 for Linux

Version 3 was the first alpha available for Linux. Chromium soon incorporated native theming for Linux, using the GTK+ toolkit to allow it fit into the GNOME desktop environment.[37][38][39][40] Version 3 also introduced JavaScript engine optimizations and user-selectable themes.[41]

Version 6 introduced features for user interface minimalism, as one of Google's goals was to make the browser "feel lightweight (cognitively and physically) and fast".[21] The changes were a unified tools menu, no home button by default (although user configurable), a combined reload/stop button, and the bookmark bar deactivated by default. It also introduced an integrated PDF reader, WebM and VP8 support for use with HTML video, and a smarter URL bar.[42][43]

Version 7 boosted performance to twice that of prior versions via hardware acceleration.[44][45][46]

Version 8 focused on improved integration into ChromeOS and improved cloud features. These include background web applications, host remoting (allowing users centrally to control features and settings on other computers) and cloud printing.[46]

Version 9 introduced a number of features, including a URL bar feature for exposing phishing attacks and sandboxing for the Adobe Flash plug-in. Other additions were the WebGL library and access for the new Chrome Web Store.[47][48][49]

2011

edit
 
Chromium logo introduced in 2011[50]

In February, Google announced that it was considering large-scale user interface (UI) changes, including at least partial elimination of the URL bar, which had been a mainstay of browsers since the early years of the Web. The proposed UI was to be a consolidation of the row of tabs and the row of navigation buttons, the menu, and URL bar into a single row. The justification was freeing up more screen space for web page content. Google acknowledged that this would result in URLs not always being visible to the user, that navigation controls and menus may lose their context, and that the resulting single line could be quite crowded.[51] However, by August, Google decided that these changes were too risky and shelved the idea.[52]

In March, Google announced other directions for the project. Development priorities focused on reducing the size of the executable, integrating web applications and plug-ins, cloud computing, and touch interface support.[53][54] Thus a multi-profile button was introduced to the UI, allowing users to log into multiple Google and other accounts in the same browser instance. Other additions were malware detection and support for hardware-accelerated CSS transforms.[55][56]

By May, the results of Google's attempts to reduce the file size of Chromium were already being noted. Much of the early work in this area concentrated on shrinking the size of WebKit, the image resizer, and the Android build system.[57] Subsequent work introduced a more compact mobile version that reduced the vertical space of the UI.[58][59]

Other changes in 2011 were GPU acceleration on all pages, adding support for the new Web Audio API, and the Google Native Client (NaCl) which permits native code supplied by third parties as platform-neutral binaries to be securely executed within the browser itself.[60][61] Google's Skia graphics library was also made available for all Chromium versions.[62][63]

Since 2012

edit
 
The Chromium Material Icon used until 2022

The sync service added for Google Chrome in 2012 could also be used by Chromium builds.[64][65] The same year, a new API for high-quality video and audio communication was added, enabling web applications to access the user's webcam and microphone after asking permission to do so.[66][67] Then GPU accelerated video decoding for Windows and support for the QUIC protocol were added.[68][69]

In 2013, Chromium's modified WebKit rendering engine was officially forked as the Blink engine.[22][23]

Other changes in 2013 were the ability to reset user profiles and new browser extension APIs.[70] Tab indicators for audio and webcam usage were also added, as was automatic blocking of files detected as malware.[71]

Version 67 added the security benefit of per-process website isolation.[18] Then version 69 introduced a new browser theme, as part of the tenth anniversary of Google Chrome.[72] The same year, new measures were added to curtail abusive advertising.[73]

Since 2021, the Google Chrome sync service can no longer be used by Chromium builds.[74][11]

Starting with version 110, only Windows 10 and later are supported for Windows users.[75]

Browsers based on Chromium

edit

In addition to Google Chrome, many other actively developed browsers are based on the Chromium code. Most of these are proprietary, like Chrome, but some remain FOSS, like Chromium.[76][77][78][79]

Proprietary

edit

Primarily non-English

FOSS

edit

Use in app frameworks

edit

These notable app frameworks embed a Chromium browser as the functional core of custom apps:

The two prominent Chromium-based WebView components also provide a similar way to make apps:

With either approach, the custom app is implemented with HTML, CSS, JavaScript, and other web technologies. Moreover, the app can be readily deployed on the operating systems supported by Chromium. Since the 2010s, many apps have been created this way. (Two examples are Spotify and Slack.)[83][84]

References

edit
  1. ^ a b c d e Google (2 September 2008). "Welcome to Chromium". Retrieved 28 April 2021.
  2. ^ a b "The Chromium Projects". Google. Retrieved 28 April 2021.
  3. ^ a b c d e Shankland, Stephen (30 November 2020). "Google gets web allies by letting outsiders help build Chrome's foundation". CNET. Retrieved 27 April 2021.
  4. ^ a b c d e f g "Chromium - Language Breakdown". Open Hub. Retrieved 19 February 2024.
  5. ^ a b c "Chromium coding style". Google Open Source. Google Source. Retrieved 22 April 2021.
  6. ^ a b "Web Platform Tests". Chromium repository. Retrieved 27 April 2021.
  7. ^ "Open-sourcing Chrome on iOS!". 2017. Retrieved 26 April 2021. Due to constraints of the iOS platform, all browsers must be built on top of the WebKit rendering engine.
  8. ^ a b "BSD license". Chromium repository. Retrieved 27 April 2021.
  9. ^ a b "Chromium Terms and Conditions". Google Code. 2 September 2008. Archived from the original on 22 October 2008. Retrieved 27 April 2021.
  10. ^ a b "Notes on Chromium". Woolyss. Retrieved 3 April 2021.
  11. ^ a b "Chromium sync Google API removed". 24 January 2021. Retrieved 20 March 2021.
  12. ^ Dougerty, Conor (12 July 2015). "Sundar Pichai of Google Talks About Phone Intrusion". The New York Times. Archived from the original on 19 July 2015. Retrieved 25 April 2019. There is a reason when we built Chrome we minimized everything to do with Chrome so that all you spent time on was the website you cared about at the given time. We wanted the users to focus on the content they were using. The reason the product was named "Chrome" was we wanted to minimize the chrome of the browser. That's how we thought about it.
  13. ^ Murphy, Glen (18 December 2012). "Why is Google Chrome browser named as Chrome?". Retrieved 6 July 2020.
  14. ^ "Google Chrome Terms of Service". www.google.com. Retrieved 26 September 2017.
  15. ^ a b "Intent to Explain: Demystifying the Blink Shipping Process". Chromium Blog. 12 November 2019. Retrieved 27 April 2021.
  16. ^ "Modern Multi-Process Browser Architecture". 22 January 2019. Retrieved 1 December 2023. Chrome was the first browser with a multi-process architecture.
  17. ^ a b "The story behind Google Chrome". YouTube. Google. Retrieved 5 December 2023.
  18. ^ a b c Kosaka, Mariko. "Inside look at modern web browser (part 1)". developer.chrome.com. Retrieved 1 December 2023.
  19. ^ "Multi-process Architecture". www.chromium.org. Retrieved 18 November 2023.
  20. ^ Pilcher, Pat (13 July 2009). "Battle of the browsers - which is master of the web?". The Independent. London. Archived from the original on 15 May 2022.
  21. ^ a b "User Experience". Chromium Developer Documentation. dev.chromium.org. 2009. Retrieved 5 July 2009.
  22. ^ a b "chrome/browser/ui - chromium/src.git - Git at Google". Chromium repository. Retrieved 20 December 2023.
  23. ^ "third_party - chromium/src.git - Git at Google". Chromium repository. Retrieved 27 April 2021.
  24. ^ Jansens, Dana (12 January 2023). "Supporting the Use of Rust in the Chromium Project". Google Online Security Blog. Retrieved 13 January 2023.
  25. ^ "Rust in Chromium". Chromium docs. Retrieved 2 December 2023.
  26. ^ "gn - Git at Google". gn.googlesource.com. Retrieved 3 December 2023.
  27. ^ "Chromium bug tracking system". Retrieved 28 April 2021.
  28. ^ "Tour of the Chromium Continuous Integration Console". Retrieved 26 April 2021.
  29. ^ Frysinger, Mike (14 March 2014). "Version Numbers". The Chromium Projects. Retrieved 1 May 2015.
  30. ^ LaForge, Anthony (16 December 2010). "Chrome Release Cycle -12/16/2010". Google Slides. Retrieved 1 May 2015.
  31. ^ Paul, Ryan (September 2008). "Google unveils Chrome source code and Linux port". Retrieved 19 June 2010.
  32. ^ Paul, Ryan (December 2008). "Google releases Chrome 1.0". Retrieved 19 June 2010.
  33. ^ "1397 - Master password is missing". bugs.chromium.org. March 2011. Retrieved 29 March 2011.
  34. ^ "812 - Profile/login support". bugs.chromium.org. March 2011. Retrieved 29 March 2011.
  35. ^ Paul, Ryan (May 2009). "Hands on: Google Chromium browser alpha for Linux". Retrieved 20 June 2010.
  36. ^ Paul, Ryan (June 2009). "Google releases Chrome preview for Mac OS X and Linux". Retrieved 20 June 2010.
  37. ^ Paul, Ryan (July 2009). "Google Chromium gains native theming support on Linux". Retrieved 20 June 2010.
  38. ^ Smith, Mike and Karen Grunberg (June 2009). "Danger: Mac and Linux builds available". Retrieved 22 June 2010.
  39. ^ Paul, Ryan (September 2009). "Chrome 3 out, JavaScript performance increased 150% since v1". Retrieved 20 June 2010.
  40. ^ Sneddon, Joey-Elijah (July 2010). "Chromium's Unified Menu Comes to Daily Builds". Archived from the original on 15 August 2010. Retrieved 15 July 2010.
  41. ^ Gruener, Wolfgang (July 2010). "Overview: Chrome 6, The Naked Browser". Archived from the original on 6 April 2012. Retrieved 14 July 2010.
  42. ^ Nakano, Chelsi (August 2010). "Chromium 7 Has Arrived and It's Not that Awesome". Retrieved 20 August 2010.
  43. ^ Gruener, Wolfgang (August 2010). "First Look: Google Increases Graphics Performance With Chrome 7". Archived from the original on 24 July 2012. Retrieved 20 August 2010.
  44. ^ a b Gruener, Wolfgang (October 2010). "A Preview of Chrome 8: Clouds Ahead". Conceivably Tech. Archived from the original on 24 July 2012. Retrieved 14 October 2010.
  45. ^ Bakke, Kurt (November 2010). "Google's Next Big Browser Play: Prerendering and False Start?". Conceivably Tech. Archived from the original on 24 July 2012. Retrieved 23 October 2010.
  46. ^ Schuh, Justin and Carlos Pizano (December 2010). "Rolling out a sandbox for Adobe Flash Player". Chromium Blog. Retrieved 1 December 2010.
  47. ^ Gruener, Wolfgang (February 2011). "Chrome 9 and 11: Instant Search, More Speed". Conceivably Tech. Archived from the original on 18 October 2012. Retrieved 6 February 2011.
  48. ^ Protalinski, Emil (16 March 2011). "Google Chrome and Chromium to get new logos". Conceivably Tech. Retrieved 10 December 2017.
  49. ^ Gruener, Wolfgang (February 2011). "Google May Kill Chrome URL Bar". Conceivably Tech. Archived from the original on 26 March 2013. Retrieved 6 February 2011.
  50. ^ Gruener, Wolfgang (August 2011). "Google Shelves Hidden Location Bar". Conceivably Tech. Archived from the original on 6 April 2012. Retrieved 9 August 2011.
  51. ^ Gruener, Wolfgang (March 2011). "Google Chrome in 2011: The Biggest Loser?". Archived from the original on 18 August 2012. Retrieved 27 March 2011.
  52. ^ Shankland, Stephen (March 2011). "Google working to reverse Chrome bloat". Retrieved 27 March 2011.
  53. ^ Gruener, Wolfgang (April 2011). "Google Preps Huge UI Update For Chrome". Conceivably Tech. Archived from the original on 6 April 2012. Retrieved 20 April 2011.
  54. ^ Paul, Ryan (June 2011). "Chrome 12 arrives with security, rendering improvements". Ars Technica. Retrieved 12 June 2011.
  55. ^ Bailey, Dan (May 2011). "Google Trims Fat From Chrome". Conceivably Tech. Archived from the original on 6 April 2012. Retrieved 5 May 2011.
  56. ^ Paul, Ryan (May 2011). "Chrome 13 introduces experimental hidden nav bar option". Ars Technica. Retrieved 19 May 2011.
  57. ^ Gruener, Wolfgang (May 2011). "Google Is Serious: You Can Kill Chrome's URL Bar". Conceivably Tech. Archived from the original on 19 April 2012. Retrieved 19 May 2011.
  58. ^ Bailey, Dan (June 2011). "No More Updates For Firefox 4, Chromium 14 Released". Conceivably Tech. Archived from the original on 6 April 2012. Retrieved 3 June 2011.
  59. ^ Paul, Ryan (September 2011). "Chrome 14 arrives with improved Lion support and NaCl". Ars Technica. Retrieved 20 September 2011.
  60. ^ Bailey, Dan (September 2011). "3D Web Browsing Sneaks into Google Chrome". Conceivably Tech. Archived from the original on 18 August 2012. Retrieved 19 September 2011.
  61. ^ Bailey, Dan (September 2011). "Google To Switch Chromium For Mac Graphics to Skia". Conceivably Tech. Archived from the original on 16 June 2012. Retrieved 19 September 2011.
  62. ^ Mathias, Raz (15 May 2012). "Keeping tabs on your tabs". Retrieved 15 May 2012.
  63. ^ Paul, Ryan (16 May 2012). "Hands-on with the new tab synchronization feature in Chrome 19". Ars Technica. Retrieved 19 May 2012.
  64. ^ Grunberg, Karen (31 July 2012). "Stable Channel Release". Retrieved 31 July 2012.
  65. ^ Paul, Ryan (31 July 2012). "Chrome 21 launches with webcam API and retina Mac support". Ars Technica. Retrieved 15 August 2012.
  66. ^ Grunberg, Karen (6 November 2012). "Stable Channel Release and Beta Channel". Chrome Releases. Google. Retrieved 6 November 2012.
  67. ^ "Issue 11125002: Add QuicFramer and friends". Chromium Code Reviews. 12 October 2012. Retrieved 25 December 2020.
  68. ^ Cho, Eddie (20 August 2013). "Chrome 29 adds a reset button". Download.com. CNET. Archived from the original on 8 April 2014. Retrieved 8 April 2014.
  69. ^ Grunberg, Karen; Xie, Daniel (14 January 2014). "Stable Channel Update". Chrome Releases. Archived from the original on 16 January 2014. Retrieved 14 January 2014.
  70. ^ "Google Chrome Browser – New Material Design – 10 Years Anniversary". TehnoBlog.org. 7 September 2018. Archived from the original on 9 March 2024.
  71. ^ Bradbury, Danny (6 December 2018). "Chrome 71 stomps on abusive advertising". Naked Security. Archived from the original on 9 December 2018. Retrieved 7 December 2018.
  72. ^ Eisinger, Jochen (15 January 2021). "Limiting private API availability in Chromium". Chromium Blog. Retrieved 20 March 2021.
  73. ^ "Chrome browser system requirements". Chrome Enterprise and Education Help. Retrieved 10 March 2024.
  74. ^ "What are the best Chrome based browsers?". NordVPN (in Portuguese). 7 June 2019. Retrieved 4 October 2024.
  75. ^ "Chromium-based browsers". Alternative to.
  76. ^ "10 Best Chromium-Based Browsers 2024". BrowserScan. Retrieved 4 October 2024.
  77. ^ "16 Best Chromium Browsers 2024 [Ranked & Reviewed]". Alvaro Trigo. 25 November 2022. Retrieved 4 October 2024.
  78. ^ "Qt WebEngine Overview - Qt WebEngine 5.11". doc.qt.io. Retrieved 9 March 2024.
  79. ^ Hildenbrand, Jerry. "What is the Android System WebView and why do so many apps depend on it?". androidcentral.com. Retrieved 9 March 2024.
  80. ^ "Introduction to Microsoft Edge WebView2". learn.microsoft.com. Retrieved 9 March 2024.
  81. ^ "Open Source - Spotify". Retrieved 1 December 2023. Here are the sources to the great Chromium Embedded Framework that is used by the Spotify Desktop client.
  82. ^ Betts, Anaïs (25 October 2016). "Building Hybrid Applications with Electron". Slack Engineering. Slack. Retrieved 1 December 2023.
edit
 
Wikimedia Commons has media related to Chromium (web browser).
Retrieved from "https://en.wikipedia.org/w/index.php?title=Chromium_(web_browser)&oldid=1256640407#Use_in_app_frameworks"