client

As suggested in the ESM guidelines of Node.js it would be good to explicit the type of the module.

{
+  "type": "commonjs",
}

The dialog currently opens on the top of my screen, even in negative position so that the title bar is mostly outside of my screen.
It also shows way off horizontally.

I would also expect it to show modally, blocking input to the settings window. At the moment you can click shortcut again, closing the previous dialog and opening a new dialog.
This is confusing and can lead to current changes

Under lib/fetch/util.js we have a few helper methods that are pretty well documented in spec and and needs to be implemented:

• appendRequestOriginHeader
• appendFetchMetadata
• TAOCheck
• corsCheck
• crossOriginResourcePolicyCheck
• makePolicyContainer
• clonePolicyContainer
• determineRequestsReferrer
• blobToFormData

Hey Crew,

Nice job on gocql, I'm a fan...

For my production services, I could use notification events (via callback or channel) when the gocql client disconnects and reconnects to/from Cassandra. This is useful for higher-level application logic (ie: invoke alarms, stop reading from a durable message queue, etc).

After looking through the code, it looks like the connection information is not p