Skip to content
C.W.K.
Quiz · 4 questions

⚖️ Reuse the Engine, Own the Browser

How a todo's engine choice was checked, priced, measured and overturned

Level 0New Tab
0 XP0/44 lessons0/13 achievements
0/100 XP to next level100 XP to go0% complete

Quiz

01Why did the todo's plan, Chromium through CEF inside a Swift window with Chrome's extensions working, fail on macOS?
02Which cost does even the shallowest Chromium fork (C1: rebrand and flags) still carry?
03What did the memory probe's "covered" run establish?
04Why does Voyager set applicationNameForUserAgent to Safari's full token, Version/<Safari's version> Safari/605.1.15?
← PreviousA Gate Before the First Brick, and Public API Only🧬 One Swift Parent, One Engine Child →One Package, Three Targets
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign in — Please sign in to comment.

No comments yet — be the first.