🌐 Website Issue | SVGs not displayed on Tor Browser with Security Level on Safest #1764

Closed
opened 2020-03-05 22:52:08 +00:00 by Zenithium · 6 comments
Zenithium commented 2020-03-05 22:52:08 +00:00 (Migrated from github.com)

Description

This issue was brought up in #275 and addressed in #308 but brought back in #1563. I guess it should be decided whether this problem will be addressed or not. Reverting to PNGs would fix this but there is more maintenance for PNGs than SVGs which was the cause of the change in the first place.

Screenshots

2020-03-05_23-50-11

## Description This issue was brought up in #275 and addressed in #308 but brought back in #1563. I guess it should be decided whether this problem will be addressed or not. Reverting to PNGs would fix this but there is more maintenance for PNGs than SVGs which was the cause of the change in the first place. ## Screenshots ![2020-03-05_23-50-11](https://user-images.githubusercontent.com/48525551/76033311-da614500-5f33-11ea-8fc6-8768251af3ee.png)
5a384507-18ce-417c-bb55-d4dfcc8883fe commented 2020-03-06 01:45:07 +00:00 (Migrated from github.com)

Same as on the other issue, are you using NoScript?

Same as on the other issue, are you using NoScript?
Zenithium commented 2020-03-06 02:39:17 +00:00 (Migrated from github.com)

This is not caused by NoScript as both disabling restrictions globally and disabling the extension completely don't fix the issue. IIRC SVGs are disabled on Safest. Try closing all tabs of the site and opening it again, since if you only enabled Safest mode and reloaded the page the SVGs will still work.

This is not caused by NoScript as both disabling restrictions globally and disabling the extension completely don't fix the issue. IIRC SVGs are disabled on Safest. Try closing all tabs of the site and opening it again, since if you only enabled Safest mode and reloaded the page the SVGs will still work.
5a384507-18ce-417c-bb55-d4dfcc8883fe commented 2020-03-06 02:49:54 +00:00 (Migrated from github.com)

This is not caused by NoScript as both disabling restrictions globally and disabling the extension completely don't fix the issue. IIRC SVGs are disabled on Safest. Try closing all tabs of the site and opening it again, since if you only enabled Safest mode and reloaded the page it will still work.

Mmm, weird, it could be a bug then.

> This is not caused by NoScript as both disabling restrictions globally and disabling the extension completely don't fix the issue. IIRC SVGs are disabled on Safest. Try closing all tabs of the site and opening it again, since if you only enabled Safest mode and reloaded the page it will still work. Mmm, weird, it could be a bug then.
Zenithium commented 2020-03-06 02:54:38 +00:00 (Migrated from github.com)

Mmm, weird, it could be a bug then.

If you set the security to Safest and then go to about:config and find svg.disabled it will be set to true, this is an intended feature. On Standard security it is set to false which is the FF default.

> Mmm, weird, it could be a bug then. If you set the security to Safest and then go to about:config and find svg.disabled it will be set to true, this is an intended feature. On Standard security it is set to false which is the FF default.
blacklight447 commented 2020-03-06 14:44:35 +00:00 (Migrated from github.com)

This is a known issue, its why i voted against the change to SVG at the time.
In any case, the amount of people running tor browser, which is also run in safest mode, is quite low.
So its not really a major issue, espeically considering as the information itself is still perfectly accesible.

Still we could see if we can make a fallback to png in here. @dawidpotocki

This is a known issue, its why i voted against the change to SVG at the time. In any case, the amount of people running tor browser, which is also run in safest mode, is quite low. So its not really a major issue, espeically considering as the information itself is still perfectly accesible. Still we could see if we can make a fallback to png in here. @dawidpotocki

This is intentional behavior as decided in #1563. Edit: If a community member submits a PR it could still be considered, but it must not impact the site for users with SVG support (i.e. the PNG fallback image must not be loaded by browsers with SVG support, even invisibly).

This is intentional behavior as decided in #1563. Edit: If a community member submits a PR it could still be considered, but it must not impact the site for users with SVG support (i.e. the PNG fallback image must not be loaded by browsers with SVG support, even invisibly).
This repo is archived. You cannot comment on issues.
No Milestone
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#1764
No description provided.