{"id":931,"date":"2024-08-08T11:35:19","date_gmt":"2024-08-08T02:35:19","guid":{"rendered":"https:\/\/blogs.igalia.com\/gyuyoung\/?p=931"},"modified":"2024-08-09T10:52:19","modified_gmt":"2024-08-09T01:52:19","slug":"chrome-ios-browser-on-blink","status":"publish","type":"post","link":"https:\/\/blogs.igalia.com\/gyuyoung\/2024\/08\/08\/chrome-ios-browser-on-blink\/","title":{"rendered":"Chrome iOS Browser on Blink"},"content":{"rendered":"\nAt the beginning of this year, Apple allowed third-party browser engines, such as Gecko and Blink, to be used on iOS and iPadOS. The Chromium community has been developing Chrome iOS based on Blink as an experimental project. This post provides an overview of the project and examines its progress during the first half of 2024.\n\n\n\n\n

Structure of Chrome iOS (w\/blink)<\/h2>\n\n\n\n\nFirst, let’s look at the overall structure of Chrome iOS. This simple diagram illustrates the structure of Chrome iOS.\n\n\n\n

\n\n\n\nThe UI components are placed in the \/\/ios\/chrome <\/em>directory, which functions similarly to the \/\/chrome layer in other implementations. The \/\/ios\/web<\/em> layer also provides APIs for its initialization, content navigation, presenting UI callbacks, saving or restoring navigation sessions and browser data, and more. The \/\/ios\/web\/public<\/em> defines the public APIs, while various other directories within \/\/ios\/web implement them. The implementation of these public APIs invokes WebKit APIs to provide the necessary functionalities.

For Chrome iOS based on Blink, the developers decided to reuse the existing iOS Chrome UI implementation last year. Thus, one of the main developments of Chrome iOS based on Blink happened in the \/\/ios\/web\/content<\/strong> <\/em>directory which is the rectangle filled by a green color, created to implement the public APIs using Blink. As you can see in the below diagram, they added the content<\/strong> directory to \/\/ios\/web<\/em> directory and implemented the public APIs using Blink’s content APIs. Notably, they’ve introduced a ContentWebState as a prototype implementation of WebState to replace the class in \/\/ios\/web\/content\/web_state<\/em>. However, as shown in the diagram, the directory currently only includes in five components: web_state<\/em>, navigation<\/em>, UI<\/em>, init<\/em>, and js_messaging<\/em>. Therefore, more components need to be implemented for Chrome iOS on Blink.\n\n\n\n\n

Igalia Contributions<\/h2>\n\n\n\n\nIgalia has been contributing to this project since the project was made public by the community. We\u2019ve worked mainly on UI related components e.g. file and color chooser, context menu, select list popup and integration with Chrome IOS UI. The pictures below are the screen captures of the chooser implementations that we contributed.


\n\n\n\n
We also helped with the features of multimedia such as the video screen capture, hardware encoding\/decoding, and audio recording.

We’ve worked on a few testing frameworks (e.g. unit tests, browser and web tests). Also, we’ve filtered out unsupported tests and failed tests. Specifically, we’ve implemented the infrastructure to run the web tests on the simulator. For your information, the test coverage of the web test on iOS Blink was about 72.2% and the pass ratio among the working tests was 91.83% at the beginning of this year. Then we’ve been maintaining the bot for Chrome iOS on Blink<\/a> to keep the build and testing because keeping build and running tests are crucial for Blink to bring up to Chrome iOS.

Besides we supported the remote debugging with DevTools on Blink for iOS<\/a>. Now developers are able to remotely use DevTools in a host machine (e.g. Mac) and inspect Chrome or Content Shell for development.

Moreover, we’ve worked on graphics stuff related to compositing and rendering. For instance, we supported the metal on ANGLE as well as fixed bugs in the graphics layers.

You can find the detailed contributions patch list here<\/a>.\n\n\n\n\n

The major changes for H1 2024 <\/h2>\n\n\n\n\nNow, let\u2019s review the major changes during the first half of this year. Firstly, the minimum iOS SDK version was bumped up to 17.4 which supports the BrowserEngineKit<\/a> library. And the [browser\/unit] tests began to run on the ios-blink bot<\/a> with the 17.4 SDK.

By reusing the existing iOS Chrome UI, ContentWebState was introduced as a prototype implementation of WebState. During H1 2024, new methods were added further or previously empty methods were implemented. For example, GetVirtualKeyboardHeight<\/em>, OnVisibilityChanged<\/em>, DidFinishLoad<\/em>, DidFailLoad<\/em> methods were implemented.

BrowserEngineKit APIs that were announced by Apple to support third-party browser engines on iOS and iPadOS have been applied to JIT, GPU, network, and content process creation.

As mentioned above, Igalia implemented a color chooser, a file chooser, and a context menu during the period.

Lastly, the package size was reduced by removing duplicated resources.\n\n\n\n\n

Remaining Tasks<\/h2>\n\n\n\n\nWe’ve briefly looked at the current status of the project so far, but many functionalities still need to be supported. For example, regarding UI features, functionalities such as printing preview, download, text selection, request desktop site, zoom text, translate, find in page, and touch events are not yet implemented or are not functioning correctly
Moreover, there are numerous failing or skipped tests in unit tests, browser tests, and web tests. Ensuring that these tests are enabled and passing the test should also be a key focus moving forward.\n\n\n\n\n

Conclusion<\/h2>\n\n\n\n\nThe Blink-based port of Chrome iOS is a large and laborious project. Igalia has made significant contributions to this project and while it is still in an early stage, more features, infrastructure and tools need to be ported to Blink. Anyhow, we believe that we are on the right track for eventually replacing WebKit by Blink on Chromium related products for iOS.\n","protected":false},"excerpt":{"rendered":"

At the beginning of this year, Apple allowed third-party browser engines, such as Gecko and Blink, to be used on iOS and iPadOS. The Chromium community has been developing Chrome iOS based on Blink as an experimental project. This post provides an overview of the project and examines its progress during the first half of […]<\/p>\n","protected":false},"author":52,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[19,4,18],"class_list":["post-931","post","type-post","status-publish","format-standard","hentry","category-igalia-chromium","tag-blink","tag-chromium","tag-ios"],"_links":{"self":[{"href":"https:\/\/blogs.igalia.com\/gyuyoung\/wp-json\/wp\/v2\/posts\/931","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.igalia.com\/gyuyoung\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.igalia.com\/gyuyoung\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.igalia.com\/gyuyoung\/wp-json\/wp\/v2\/users\/52"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.igalia.com\/gyuyoung\/wp-json\/wp\/v2\/comments?post=931"}],"version-history":[{"count":79,"href":"https:\/\/blogs.igalia.com\/gyuyoung\/wp-json\/wp\/v2\/posts\/931\/revisions"}],"predecessor-version":[{"id":1013,"href":"https:\/\/blogs.igalia.com\/gyuyoung\/wp-json\/wp\/v2\/posts\/931\/revisions\/1013"}],"wp:attachment":[{"href":"https:\/\/blogs.igalia.com\/gyuyoung\/wp-json\/wp\/v2\/media?parent=931"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.igalia.com\/gyuyoung\/wp-json\/wp\/v2\/categories?post=931"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.igalia.com\/gyuyoung\/wp-json\/wp\/v2\/tags?post=931"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}