You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think this is default behavior with what I have set as the "default browser" (Safari). But kind of expect from a user perspective that it would open in Chrome, since the browser is already being used via the extension.
Additionally, Safari when "sending", does not allow me to scan a QR code via the laptop camera (Chrome does however, hence it would be nice if the wallet opened in Chrome).
I am a first time user of the Trezor so this is one of my initial impressions.
The text was updated successfully, but these errors were encountered:
On Jun 10, 2017 4:25 AM, "Dimas Begunoff" ***@***.***> wrote:
I think this is default behavior with what I have set as the "default
browser" (Safari). But kind of expect from a user perspective that it would
open in Chrome, since the browser is already being used via the extension.
Additionally, Safari when "sending", does not allow me to scan a QR code
via the laptop camera (Chrome does however, hence it would be nice if the
wallet opened in Chrome).
I am a first time user of the Trezor so this is one of my initial
impressions.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#18>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAGZ8bhpzUJEZbccAjyK8f6Q8FseDT9dks5sCf6LgaJpZM4N1_Bo>
.
I think this is default behavior with what I have set as the "default browser" (Safari). But kind of expect from a user perspective that it would open in Chrome, since the browser is already being used via the extension.
Additionally, Safari when "sending", does not allow me to scan a QR code via the laptop camera (Chrome does however, hence it would be nice if the wallet opened in Chrome).
I am a first time user of the Trezor so this is one of my initial impressions.
The text was updated successfully, but these errors were encountered: