e10s in its current form probably brings some fingerprinting risks with it. e.g. users of accessibility tools won't have e10s enabled on Windows and macOS at least. Windows XP users with D3D9 support neither. mcs and brade found that showModalDialog() is not available when e10s is enabled etc.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
users of accessibility tools
not only those users, but
Also, on a Microsoft Surface Pro / Windows 10 that with a11y enabled: <Multiprocess Windows 0/1 Dissabled by accesibility tools>.
https://bugzilla.mozilla.org/show_bug.cgi?id=1329752#c26
a11y enabled by default on all touch screens.
Set dom.disable_window_showModalDialog to true to fix the obvious part of this ticket without patching.
But that prevents the parent process from using that feature as well, right? Do we have some estimate about what that would break? (We'd need a patch for actual review)
It is for non-e10s only. As you see it is already disabled in e10s and removed in upstream. Some legacy things would break in non-e10s, but that's not what we should take care of. (So you want the backported patch to remove it completely, but it looks better to keep the pref, if somebody would complain.)
r=mcs
The patch looks good to me and it seems to work. I tested it on macOS and, with or without e10s enabled, calling window.showModalDialog() generates a TypeError: window.showModalDialog is not a function exception.
This ticket was filed to investigate the differences between modes, but closed as fixed without mentioning the results of it. What was found during RFP project?
mcs mentioned this fix will no longer be needed in TBB/ESR60 because of the patches landed in https://bugzilla.mozilla.org/show_bug.cgi?id=981796
Not comment:2?
Does upstream team agree with your ff60-esr-obsolete or can prove ff60-esr-will-have?
This ticket was filed to investigate the differences between modes, but closed as fixed without mentioning the results of it. What was found during RFP project?
mcs mentioned this fix will no longer be needed in TBB/ESR60 because of the patches landed in https://bugzilla.mozilla.org/show_bug.cgi?id=981796
Not comment:2?
Does upstream team agree with your ff60-esr-obsolete or can prove ff60-esr-will-have?
I think ESR60 is different enough that we could think about filing a new ticket thinking about the remaining things to do wrt to e10s/non-e10s fingerprintability, if there are any left at all.