SVG isn't blocked in Safest security setting with 8.0a9

SVG doesn't seem to be blocked in Safest security setting with 8.0a9 (Linux)

added TorBrowserTeam201807R component::applications/tor browser ff60-esr owner::tbb-team priority::high resolution::fixed severity::normal status::closed tbb-security-slider type::defect labels

Looking at about:support one does find

svg.in-content.enabled false

Replying to cypherpunks:

SVG doesn't seem to be blocked in Safest security setting with 8.0a9 (Linux)

What makes you believe so? Do you have an example that is blocked in Tor Browser stable but not in the alpha?

Trac:
Status: new to needs_information

Replying to gk:

Replying to cypherpunks:

SVG doesn't seem to be blocked in Safest security setting with 8.0a9 (Linux)

What makes you believe so? Do you have an example that is blocked in Tor Browser stable but not in the alpha? I just noticed that quickly while going into my Github account and trying to report an issue and I saw that the "edit" button icon was present when normally it wasn't with the stable series [I may be wrong though if Github added a png fallback, so very sorry in that case for my misleading report] (as well as the non-presence of the canvas anti-fp notification on first visit to Github, though that may be a fix in Firefox?)

Replying to cypherpunks:

Looking at about:support one does find

svg.in-content.enabled false

Looking at https://bugzilla.mozilla.org/show_bug.cgi?id=1216893, it looks like the correct pref name is now svg.disabled. Does the incorrect behavior you observed disappear if you use about:config to set that pref to false?

Replying to mcs:

Looking at https://bugzilla.mozilla.org/show_bug.cgi?id=1216893, it looks like the correct pref name is now svg.disabled. Does the incorrect behavior you observed disappear if you use about:config to set that pref to false? I can confirm.

Trac:
Status: needs_information to new

What?! Again?! Now the reversed #21885 (moved). Also check for #16607 (moved).

Trac:
Keywords: N/A deleted, ff60-esr, tbb-security-slider, TorBrowserTeam201807 added

Trac:
Cc: N/A to arthuredelstein

Trac:
Priority: Medium to Very High

Trac:
Priority: Very High to High

I confirmed we need to update the pref name. Here's a patch that does that:

https://github.com/arthuredelstein/torbutton/commit/26590

Trac:
Keywords: TorBrowserTeam201807 deleted, TorBrowserTeam201807R added
Status: new to needs_review

Looks good to me. Merged to master (commit 54c64d2ea862873a42e6049e2e1aa2bc4a5b2b27)

Trac:
Status: needs_review to closed
Resolution: N/A to fixed

closed

mentioned in issue #26670 (moved)

moved to tpo/applications/tor-browser#26590 (closed)