TrasherDK

Or even better. Fix it at the source.

@zsakowitz Thanks for the explanation. Even I got something from that.

I guess nobody is home :cry: This code: ```js import JSEncrypt from 'node-jsencrypt' import { readFileSync } from 'fs' import path, { resolve } from 'path' import { fileURLToPath }...

@nanostos is right. Even ATM's had this, until a few years back, they dropped decimals completely. They don't spit out coins anyway :smile:

@nanostos Again, I agree :laughing: App's like this should target the end-user. Not the dev, who presumably thinks very differently, compared to some low paid till operator.

Too much tracking and goggle ads for my taste.

Same error on `Windows 8.1`  Links to pre windows 11 versions would be appreciated :cry:

```js const autoCompleteJS = new autoComplete({ selector: "#autoComplete", placeHolder: "Buscar...", searchEngine: "strict", data: { src: async (query) => { try { const source = await fetch(`/search-autocomplete?q=${query}`); const data = await...

Open the link in a new window, with response having correct type.

I did the `window.open(selection.url, '_blank')` thingy and server-side, in PHP, letting the endpoint set `application/octet-stream` in the response.