Thortok2000 wrote:If you notice in the screenshot, the only way to delete 'other site and plug-in data' is to also delete cookies. And the only way to NOT delete 'other site and plug-in data' is to NOT delete cookies.
So somehow Chrome is throwing plugins in with cookies. Why I don't know. But that's probably why setting it for cookies also sets it for plug-ins. WME Toolbox is basically a plug-in.
Damnedest thing I've seen in a while. Part of what got me thinking about it was that when I would display cookie information for the domain, there'd be the usual entries you'd expect to see for a cookie reference, but there was also a "Local Storage" section as well. Clicking on that would only show how much space was being used - not anything pointing to the content (which was part of what made it hard to determine if it was the storage for the extension/plugin as it interacts with the Waze domain). So I took a blind shot, given that nothing else was working, and voila! It worked. Go figure.
Well, at least if someone else using Chrome is having problems like this in the future, we now know that we need to tell them to allow *.waze.com cookies to persist - if they're clearing cookies they need to except that domain from the cleaning.