Actually it looks like we've got a handful of instances of this same assertion failing in other tests (based on a bugzilla search for the assertion text). bug 1780143 bug 1780558 bug 1780590 bug 1780590 bug 1826361 (this bug here) All of the instances seem to be in tests that are explicitly testing or toggling the resistFingerprinting pref. This particular test, `mq_prefers_color_scheme_light.html`, gets run with the pref explicitly-enabled: ``` test-pref(privacy.resistFingerprinting,true) == mq_prefers_color_scheme_light.html greenbox.html ``` So this seems to be a persistent assertion-failure bug in the resistFingerprinting functionality, which crops up now and then in different tests that are exercising the feature.
Bug 1826361 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Actually it looks like we've got a handful of older instances of this same assertion failing in other tests (based on a bugzilla search for the assertion text). bug 1780143 bug 1780558 bug 1780590 bug 1780590 bug 1826361 (this bug here) All of the instances seem to be in tests that are explicitly testing or toggling the resistFingerprinting pref. This particular test, `mq_prefers_color_scheme_light.html`, gets run with the pref explicitly-enabled: ``` test-pref(privacy.resistFingerprinting,true) == mq_prefers_color_scheme_light.html greenbox.html ``` So this seems to be a persistent assertion-failure bug in the resistFingerprinting functionality, which crops up now and then in different tests that are exercising the feature.