#33184: Support for Fenix
----------------------------------------------+----------------------------
Reporter: sisbell | Owner: gk
Type: enhancement | Status: assigned
Priority: Very High | Milestone:
Component: Applications/Tor Browser | Version:
Severity: Normal | Resolution:
Keywords: tbb-mobile, TorBrowserTeam202005 | Actual Points:
Parent ID: #33659 | Points:
Reviewer: | Sponsor:
| Sponsor58-must
----------------------------------------------+----------------------------
Comment (by acat):
I noticed that there is the `EARLY_BETA_OR_EARLIER` define which controls
several prefs, for example the one controlling whether `SharedArrayBuffer`
is enabled or not (not implying that `SharedArrayBuffer` is still
dangerous, just as an example). And by taking a look at the latest Fenix
releases:
{{{
v4.1.0
36.0.2
75.0.20200309155231
EARLY_BETA_OR_EARLIER=1
has SharedArrayBuffer
}}}
{{{
v4.2.0
37.0.0
75.0.20200322132212
EARLY_BETA_OR_EARLIER=
does not have SharedArrayBuffer
}}}
{{{
v4.3.0
38.0.0
76.0.20200406152003
EARLY_BETA_OR_EARLIER=1
has SharedArrayBuffer
}}}
{{{
v5.0.0
39.0.1
76.0.20200424000239
EARLY_BETA_OR_EARLIER=
does not have SharedArrayBuffer
}}}
I'm not sure if it's intended that there is one Fenix version with early
beta and another with late beta alternatively, or it is a coincidence.
This might not be an issue if they are going to move to gecko-release for
Fenix release, but just mentioning it here just in case we want to take a
look at these kind of issues. With some pinning tests like the
`dom_enumeration` ones, but for `prefs` we should probably be able to
catch these issues, so that might be a good idea to have for Fenix.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33184#comment:22>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
