We're working on extensions and Adblock right now, so should be out soon!
For CMD-W, we're trying to change how you think about pages to something you "mark as done" as opposed to just "close", and changing the shortcut helps make that change for users.
Try it out and let me know if you think it's necessary to support CMD-W :)
Please don't force users to un-learn years of what they already know. It doesn't matter if you call it "closing" a page or "marking it as done" but _please_ make well-known keyboard shortcuts do roughly what a user would expect.
We're testing out a classic mode at the moment that allows your current shortcuts to work as well :)
Everyone expects a very specific thing, make the current thing go away. Its the same reason you likely picked CMD-k as the shortcut to your pop up window. That's what Slack does along with several other applications.
If you want to map this shortcut to your implementation of "going away" that's fine but it should be the same command.
Right now, it shows a message on the bottom-left asking if you meant to close a page and suggesting "D" as the shortcut instead.
I think adding a classic mode with those shortcuts enabled should solve the issue. What do you think?
I've experienced the likely same outcome with Vimium and 'x'
I suspect you will want to have modifier keys be the default. Something to ask users rather than forcing them to adopt to what you think is best
Right now, if you accidentally close a page, you can quickly "Z" (or click the undo button that shows up) to bring the page back.
This closes the tab, and on restore, the partial input is lost. Had this hit me more than once on Confluence
We think apps like Superhuman have brought the idea of single-key shortcuts into the forefront, and we really like how much more memorable they are for most users.
We'll definitely learn from our users' feedback though, and we'll work on a solution with them if they have issues with it :)
edit: implementing Chrome extension API. All Chrome extensions will be available :)
Do you find that your decision to use WebKit is getting in your way here?
As it happens, my company is also working on a browser for a niche userbase (not competing with you!), and I decided to go with Electron rather than Microsoft's WebView2 because it seemed to me that that option would give us more flexibility to deeply customize both the chrome and the content. Our target user base is mostly on Windows, not Mac, so Apple WebKit wasn't on the table for us.
I think WebKit helped a lot initially getting everything running. Not having access to extensions and other limitations imposed by Apple is a bit of a bummer (which I'm working around), but I think it's been much better than using Chromium/Electron still (especially on performance!)