Original Summary

Hi all, One of the strict constraints in Chrome's Manifest V3 architecture is that sandboxed extensions cannot mutate the browser's C++ native UI frame (tabs, omnibox, and toolbar). To solve this, I built Chrome Appearance Switcher using Chrome's Native Messaging API to interface directly with Windows OS theme dispatchers. The Architecture: Frontend (MV3) : Clean glassmorphic popup with a Sun/Moon interactive toggle, live SVG browser mockup preview, and keyboard shortcut listener ( Alt + Shift + D ). IPC Communication : Uses length-prefixed standard I/O byte streams to talk to a native companion. OS Dispatcher : Updates AppsUseLightTheme in HKCU\Software\Microsoft\Windows\CurrentVersion\Themes\Personalize and issues a SendMessageTimeout broadcast for WM_SETTINGCHANGE ( 0x001A ). Chrome repaints instantly with sub-20ms latency. Self-Contained Installer Generator : Because users dislike manually configuring native messaging manifests, the extension dynamically generates and downloads a 1-click self-contained .bat installer with the active extension ID already embedded. The project is completely free, open-source under MIT, and just got approved on the Chrome Web Store: Chrome Web Store : https://chromewebstore.google.com/detail/chrome-appearance-switche/giipkopljmnjmlkecknneemdkobcapnk Source Code : https://github.com/tljafar/chrome-appearance-switcher Happy to answer any questions about MV3 native messaging or Windows theme IPC!   submitted by   /u/Desperate-Charge2302 [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/11 12:53:42