bigskysoftware / bigskysoftware/_hyperscript

Handling exceptions for writeText()

Aperta
#565 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
JavaScript
Stelle
3.8k
Fork
172
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

I'm unable to handle exception while a coping text to a clipboard idiomatically. Maybe it's not the only place for such behavior but it's the only one I've found.

I'm using qutebrowser and I've blocked programmatic access to a clipboard for websites.
Unfortunately, I don't know how to block access the same way for other browses =\

**Use case**: I want to show a notification that user has successfully copied text to the clipboard or if there is an error. To do so I have to handle exception that writeText() might throw.

I expect the following code to work:
```html

Copy

--
```
Output shows **Success** and console logs `Uncaught (in promise) DOMException: Write permission denied.`. `catch` doesn't seem to work.

There is another way to catch exceptions for an element (`on exception`):

```html

Copy

--
```

The same result: output shows **Success** and console logs `Uncaught (in promise) DOMException: Write permission denied.`.

Feels like exception isn't related to the element in any way.

## Sanity check

Just to make sure that exceptions are catchable:

```html

Copy

--
```
Shows **Error: I am thrown manually** in output and console is clean.

```html

Copy

--
```

This one is interesting. It shows **Error:** in output and picrelated in console

![image](https://github.com/user-attachments/assets/7c411767-d1ec-4a39-875f-ab1df4994397)

## Workaround

I've managed to get it working by calling writeText() in a more traditional way:

```html

Copy

--
```
Output has **Error: NotAllowedError: Write permission denied.** and a clean console.

```html

Copy

--
```

This one behaves the same way it does in sanity check. In catches the exception but error is empty while console has the following:

![image](https://github.com/user-attachments/assets/12685deb-e38a-4166-b148-ec74e75804b9)

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Direzione di ricerca

Riproducete il problema con gli esempi HTML forniti, confrontando il comando writeText() con la chiamata a navigator.clipboard.writeText(). Tracciate il modo in cui la promise degli appunti rifiutata viene gestita da catch e on exception, quindi verificate che l'errore raggiunga il gestore senza segnalare il successo né registrare un rifiuto non gestito.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
javascript
Ambito
frontend, web-dev
Tipo di issue
Bug
Difficoltà
3/5
Tempo stimato
1-2 giorni
Stato di attività
Ferma
Chiarezza
Abbastanza chiara
Idoneità per principianti
42/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.