Unfortunately this is another case of throwing the baby out with the bathwater, and incidentally not really solving the problem.
Firstly there are various kinds of cookies. There are ones that are stored on your hard-disk, and others which exist only in memory (for the life of the browser instance.)
There are ones used for marketing and tracking purposes, and others (notably session cookies) that allow the server to track the "state" - thus allowing for "web apps" as much as web-pages.
So their idea is to just "ban cookies". Or, as they have done, get all sites to have a "allow cookies" switch. Don't turn that on? well then you can't use any part of the site.
And if you do turn it on, it's "all or nothing" - I can't allow say _just_ the session cookie, while banning the tracking cookies?
As to the possibility of enforcing this? Let's not even go there...
what other option is there? To mandate browser source code that implements cookies in a lawful way?
And where is the broad coalition of "don't be evil" browser vendors and websites that proudly claims "we don't track you" and that would have made such laws unnecessary?
Firstly there are various kinds of cookies. There are ones that are stored on your hard-disk, and others which exist only in memory (for the life of the browser instance.)
There are ones used for marketing and tracking purposes, and others (notably session cookies) that allow the server to track the "state" - thus allowing for "web apps" as much as web-pages.
So their idea is to just "ban cookies". Or, as they have done, get all sites to have a "allow cookies" switch. Don't turn that on? well then you can't use any part of the site. And if you do turn it on, it's "all or nothing" - I can't allow say _just_ the session cookie, while banning the tracking cookies?
As to the possibility of enforcing this? Let's not even go there...