YabYab runs Chrome extensions on WebKit’s own extension engine, the one Safari uses. Where Chrome has something WebKit doesn’t, such as bookmarks, history, downloads, side panels, notifications, speech or signing in with your Google account, Yab fills it in, so most extensions work as they do in Chrome.
Add one#
- On the extension’s page in the Chrome Web Store, press Add to Yab, where Chrome’s button was.
- Or in Settings › Extensions, press Add Extension and paste a store link or an extension’s id. A link already on the clipboard is picked up by itself.
- Or bring the ones you use from Chrome, Arc, Dia, Brave or Edge: they are downloaded fresh from the store.
Before anything is added, Yab says in plain words what the extension will be able to do, such as Read and change every site you visit. Each download’s signature is checked against the extension before it is unpacked. Extensions update themselves; an update that wants more asks first.
Use them#
Site Controls, the sliders at the end of the tab you are on (with tabs across the top) or at the end of the address, opens your extensions; so does ⌘E. Pin the ones you use most: they sit as tiles at the top, and 1 to 8 press them. Right-click one to pin it, open its options, reload or remove it.
Each one’s settings#
In Settings › Extensions, click an extension for its page: switch it off, give its commands keys, or let it draw your new tab page. Choose whether it reads pages on all the sites it requested, or only on specific sites you add to Allowed sites. When offered, On click limits it to the page you press it on. Blocked sites stay blocked in every mode. Extensions stay out of private tabs unless you turn on Allow in private tabs.
Your own#
Load Unpacked… takes a folder with a manifest.json. After each change, press Reload on its page, as in Chrome’s developer mode. Native messaging works with hosts registered for Chrome, Edge, Brave or Arc.