New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: QR Code Unscannable in dark mode on Samsung Internet browser #5860
Comments
It's "interesting" how the Samsung Internet browser applies its own dark theme and even overrides the webpage's settings. You can temporarily circumvent this by switching to the Light mode in the browser's setting — you'll stiill be able to use our dark mode afterwards and also see the proper colors ;) I will submit a PR that incorporates the |
Potentially fixes btcpayserver#5860.
Checked with v24.0.7.1 and this doesn't seem to be fixed. |
Potentially fixes btcpayserver#5860.
Potentially fixes btcpayserver#5860.
It still behaved the weird way even with v25 of the browser. According to the ongoing discussion on the forum, Samsung seems to be convinced that managing these preferences manually via the settings if you don't want their proprietary default seems to be the way to go. We cannot help with that. |
What is your BTCPay version?
v1.13.0
1fe766c
How did you deploy BTCPay Server?
Manual
What happened?
When attempting to pay an invoice using Checkout V2 using Samsung Internet browser with dark mode enabled, the SVG QR code is modified by the browser and becomes unscannable.
Screenshot:
How did you encounter this bug?
Relevant log output
No response
What browser do you use?
Additional information
I found this post on Samsung forums: https://forum.developer.samsung.com/t/websites-dark-mode-gets-overridden-by-samsung-internets-dark-mode/22937/27 . The most recent comment is interesting:
I tried adding
<meta name=”color-scheme” content=”light dark”>
to the<head>
of Checkout V2, but it did not have any impact on the issue. This is because the latest version of Samsung Internet available for my device is v23.Are you sure this is a bug report?
The text was updated successfully, but these errors were encountered: