New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ToDo: diffs FF109-FF110 #1640
Comments
some bugzilla tickets
|
thanks E .. have some 🥮 |
I wonder if we should enforce without digging too far back, this was enabled FF104 1750972, now disabled. That's half a year. Clearly not a massive breakage, and they are flipping back out of an abundance of precaution. @fxbrit what say you fishy 🎣 ? we're using HoM so scheme must be the same (that's what the "only" part means - no insecure fallbacks even for subresources), so I guess really it doesn't make a difference - perhaps we should just ignore it and let Mozilla eventually flip it again in future ? |
for clarity, do you mean that only my understanding of the bugzilla is that the HTTP page is setting a also cool stuff lulz --> https://bugzilla.mozilla.org/show_bug.cgi?id=1812195#c0 |
my understanding is (and PB mode is HTTPS-First, not HoM) that we never connect to HTTP because we always try HTTPS first and with AF's settings we never even test if an insecure version exists and timeout to the interstitial. For HoM, schemeful doesn't even apply since everything will be HTTPS, same scheme, as per the "only" part - cogito ergo sum, right? amiright? so, as per my linked bugzilla comment, this does not affect us - it only affects some sites with HoM exceptions (took 6 months for someone to complain about it and get it flipped) - so we could either set that pref, or ignore it and one day moz will flip it back on (maybe they never do) - I do not expect our users to be using insecure sites, and I'd rather not have the maintenance burden - but if you think we should add it, then confirm - otherwise I'm happy to close this and move on |
FWIW: Windows only |
then let's leave it alone, we're not chasing standard's compliance. I think eventually Mozilla will flip it because they want to adhere to https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite (as they should). |
FF110 is scheduled for release Feb. 14th
FF110 release notes
FF110 for developers
FF110 security advisories
88 diffs ( 40 new, 34 gone, 14 different )
changed in v110.0:
lvl2PBM
- 1763660, 1776760, 1778457, 1783496, 1808212 part3ignore
click me for details
==NEW
==REMOVED, RENAMED or HIDDEN
==CHANGED
The text was updated successfully, but these errors were encountered: