W3C home > Mailing lists > Public > public-tracking@w3.org > June 2012

Re: Today's call: summary on user agent compliance

From: イアンフェッティ <ifette@google.com>
Date: Wed, 13 Jun 2012 16:38:21 -0700
Message-ID: <CAF4kx8dB9+_NMDf8MwN0tJho4uKYDkX-sK8dnsPma3bkT=4xgA@mail.gmail.com>
To: Rigo Wenning <rigo@w3.org>
Cc: Kevin Smith <kevsmith@adobe.com>, "Roy T. Fielding" <fielding@gbiv.com>, "<public-tracking@w3.org> (public-tracking@w3.org)" <public-tracking@w3.org>
Because I thought we said earlier (in DC) that we expected browsers would
only show exception UI in response to a user gesture. Otherwise, you end up
with popups on every page (which apparently some people think is an OK

On Wed, Jun 13, 2012 at 4:04 PM, Rigo Wenning <rigo@w3.org> wrote:

> On Wednesday 13 June 2012 15:50:23 Ian Fette wrote:
> > You say "you can trigger an exception" but that's a HECK of a lot
> > harder for a third party to do.
> Ian,
> you said, "if I do not respond, I'm not on the hook".
> This is something else then saying: "I will never ever accept any
> token from UA string IE".
> And to trigger an exception is actually a good test. I still believe
> that we should arrive in the 21th century. That means we have to
> start thinking about what it makes a HECK less hard for a third
> party to trigger an exception.
> If this is all about revenue and not about technology and users, you
> could negotiate every cookie directly with the FTC or the
> Commission.
> But I hope I can tease you to better technology. So how can we make
> exceptions easier? You say it's hard. Why? Because of the origin
> constraints?
> Rigo
Received on Wednesday, 13 June 2012 23:38:50 UTC

This archive was generated by hypermail 2.3.1 : Friday, 3 November 2017 21:44:51 UTC