@[email protected] to [email protected]English • 2 months agoFirefox 132 Enters Beta with Support for Blocking Third-Party Cookie Access - 9to5Linux9to5linux.comexternal-linkmessage-square12fedilinkarrow-up1103arrow-down14
arrow-up199arrow-down1external-linkFirefox 132 Enters Beta with Support for Blocking Third-Party Cookie Access - 9to5Linux9to5linux.com@[email protected] to [email protected]English • 2 months agomessage-square12fedilink
minus-square@[email protected]linkfedilink-4•2 months ago However, please keep in mind that this is a pre-release version not intended for production use as it may lead to data loss. … “Production”? “Data loss”? It’s a browser.
minus-square@[email protected]linkfedilink5•2 months agoAre you joking? A lot of people do most of their work in browsers these days. Having cookies suddenly misbehave can lead to severe data loss.
minus-square@TyfudlinkEnglish4•2 months agoPeople use web browsers to do their job. Which requires data storage.
minus-square@[email protected]linkfedilink1•2 months agoI would imagine anything more than session info would be stored to LocalStorage, then promptly sent to the server.
minus-square@[email protected]linkfedilink0•2 months agoThe 132 update caused a bunch of people’s toolbars to go haywire, so it seems like a worthwhile warning to put out.
… “Production”? “Data loss”? It’s a browser.
Are you joking? A lot of people do most of their work in browsers these days. Having cookies suddenly misbehave can lead to severe data loss.
Fair enough!
People use web browsers to do their job. Which requires data storage.
Cookies are used for storing data, fwiw.
I would imagine anything more than session info would be stored to LocalStorage, then promptly sent to the server.
You’d think so, and yet… not always lol
The 132 update caused a bunch of people’s toolbars to go haywire, so it seems like a worthwhile warning to put out.