all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Luis Felipe <luis.felipe.la@protonmail.com>
To: Timo Wilken <timo@twilken.net>
Cc: help guix <help-guix@gnu.org>
Subject: Re: Icecat and Chromium don't activate the right color scheme of websites
Date: Wed, 08 Mar 2023 16:35:14 +0000	[thread overview]
Message-ID: <oQRvriX9IvlZn1xImS8RiKxX1NuRerxWgNdkty2xRk_rBD9X5btzPzRxOeBrvSpm7xfezd8eWQBY4Opb6HOSrcI3-dXolYzDcygzBnSQvmw=@protonmail.com> (raw)
In-Reply-To: <DFABDBC4-2269-49F3-8618-E0A7ECA5DF16@twilken.net>


[-- Attachment #1.1: Type: text/plain, Size: 896 bytes --]

Hi Timo,


On Wednesday, March 8th, 2023 at 15:12, Timo Wilken <timo@twilken.net> wrote:

> > QUESTIONS
> > 

> > Do you know of any defaults in Icecat or Chromium that might be preventing the expected functionality from working correctly? As far as I understand the versions of both Icecat and Chromium in Guix are supposed to support all the features required for automatic color scheme activation to work.
> 

> It works for me if I disable IceCat's "resist fingerprinting" option (search for "fingerprint" on about:preferences). I assume that sites can fingerprint your browser based on its theme (light or dark), which is presumably why this option disables the CSS feature.

Aha, indeed.

The option is also available from the Application menu → IceCat Settings → Privacy and Security.

Thanks for checking, Timo, I'll check for similar settings in Chromium.

Cheers,

[-- Attachment #1.2: publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc --]
[-- Type: application/pgp-keys, Size: 1722 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 509 bytes --]

      reply	other threads:[~2023-03-08 16:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08 15:01 Icecat and Chromium don't activate the right color scheme of websites Luis Felipe
2023-03-08 15:12 ` Timo Wilken
2023-03-08 16:35   ` Luis Felipe [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='oQRvriX9IvlZn1xImS8RiKxX1NuRerxWgNdkty2xRk_rBD9X5btzPzRxOeBrvSpm7xfezd8eWQBY4Opb6HOSrcI3-dXolYzDcygzBnSQvmw=@protonmail.com' \
    --to=luis.felipe.la@protonmail.com \
    --cc=help-guix@gnu.org \
    --cc=timo@twilken.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.