can't get chrome to ask about cookies anymore

[Andrew Benton]

has the chromium dev team decided to permanently remove the ability
for me to tell chrome to ask me about each cookie that a domain is
trying to save? i was rather enjoying the easy control that i got from
the popups asking me about each cookie, but now i can only block or
allow. i'm running the latest dev build on ubuntu linux. is anybody
else encountering the same?

it seems to me the ui around content settings could use a lot of
feedback from people actually using it. are there people on the
chromium team listening to complaints about that particular area?

cheers,
amb

[Mattias Nissler]

+jochen

There's work underway to improve the experience for the case sites try to set many cookies, the prompts are due to be replaced by something more comfortable (basically collecting all prompts into one). Jochen is the expert on that, he certainly can tell you more.

--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
   http://groups.google.com/a/chromium.org/group/chromium-discuss

[Jochen Eisinger]

The feature is under development, the prompt mode is still available
on beta/stable channels. Basically, you'd set the cookie settings to
block. Then click on the blocked cookies icon and click on the new
"show cookies etc.." button. That will open a dialog where you see all
blocked/allowed cookies, and can create rules for them.

-jochen

[Andrew Benton]

thanks for the replies guys. i have seen the beginnings of the new interface in the linux dev channel and i think i like it. stuff just hasn't been wired up yet. i hit allow for the cookie sets i want to allow but no rules are created. i can see what the plan is though. is it working on the windows branch?

any plans to do a similar thing for javascript? it'd be nice to allow or deny javascript based on the hosting domain rather than just all or nothing based on the domain serving the resources.

last question: what's the deal with the matching patterns on js and cookie rules? is [*.]google.com supposed to match google.com as well as e.g. mail.google.com or mailgoogle.com? if there is supposed to be matching it has never worked for me. for instance, i need to have separate cookie rules for [*.]meetup.com and [*.]www.meetup.com. just wondering whether i'm doing something wrong.

thanks for the incredible work on chromium so far. it's an amazing piece of software.

cheers,

amb

[Jochen Eisinger]

On Sat, Jul 31, 2010 at 7:23 PM, Andrew Benton <andrew...@gmail.com> wrote:
> thanks for the replies guys. i have seen the beginnings of the new interface
> in the linux dev channel and i think i like it. stuff just hasn't been wired
> up yet. i hit allow for the cookie sets i want to allow but no rules are
> created. i can see what the plan is though. is it working on the windows
> branch?
> any plans to do a similar thing for javascript? it'd be nice to allow or
> deny javascript based on the hosting domain rather than just all or nothing
> based on the domain serving the resources.
> last question: what's the deal with the matching patterns on js and cookie
> rules? is [*.]google.com supposed to match google.com as well as e.g.
> mail.google.com or mailgoogle.com? if there is supposed to be matching it
> has never worked for me. for instance, i need to have separate cookie rules
> for [*.]meetup.com and [*.]www.meetup.com. just wondering whether i'm doing
> something wrong.

[*.]meetup.com should match www.meetup.com but not e.g. foomeetup.com.
If that's not the case for you, please file a bug including steps how
to reproduce.

thanks
-jochen