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

Re: Opt-back-in Information API (ACTION-94)

From: Sid Stamm <sid@mozilla.com>
Date: Wed, 25 Jan 2012 12:44:35 -0800 (PST)
To: Shane Wiley <wileys@yahoo-inc.com>, Jonathan Mayer <jmayer@stanford.edu>
Cc: "public-tracking@w3.org (public-tracking@w3.org)" <public-tracking@w3.org>
Message-ID: <4c288439-f30e-43be-8d2e-6e6f07ed433d@zimbra1.shared.sjc1.mozilla.com>
Shane, Johnathan,

Sorry I couldn't make it to Brussels with everyone, so I may be missing a little context here.  I'm assuming these proposals are for specification and not for non-normative examples in the document.  Please correct me if I'm wrong here!

Shane Wiley Wrote:
> Doesn't this promote a UI treatment to some degree?  

The proposal does indeed appear to limit the degree to which user agent software can communicate with our users.  Can we focus on specifying how web sites interact with the user agent (via API) and not on the actions the user agent takes?  For example, off the top of my head:

Rough Proposal:

"boolean requestSiteSpecificTrackingException(String domain,
[optional] String notificationText, [optional] moreURL)

"The requesting site calls this function to invoke the User 
Agent's exception granting mechanism (for examples of potential 
designs, see section #.#.#).  The notificationText is offered 
as a human-readable reason for the exception, and an optional 
moreURL for additional information provided by the entity 
requesting the exception."

Not the best words here, but hopefully my intention is clear.

> I believe our
> language was built to avoid the UI treatment and instead provide the
> raw elements to allow multiple UI treatments to occur (text + link).

I agree with Shane here.

-Sid

>  I believe your proposal is asking instead of provide a top-line
> message to users with a link to more, you'd rather simply send the
> user to the "learn more" link.  I'd rather the two stage approach
> (even with suggested language to make sure we're not attempt to hide
> anything from users) but believe forcing them to the full page will
> be considered a negative outcome by many users (more "pop-up"
> windows with even greater text).
> 
> - Shane
> 
> -----Original Message-----
> From: Jonathan Mayer [mailto:jmayer@stanford.edu]
> Sent: Wednesday, January 25, 2012 4:59 PM
> To: public-tracking@w3.org (public-tracking@w3.org)
> Subject: Opt-back-in Information API (ACTION-94)
> 
> Proposal:
> 
> boolean requestSiteSpecificTrackingException(String domain,
> [optional] String notificationText, [optional] moreURL)
> 
> The browser prompts the user with text and a link to learn more about
> the opt-back-in request.
> 
> Alternative proposal:
> 
> boolean requestSiteSpecificTrackingException(String domain,
> [optional] String notificationURL)
> 
> The browser renders a page (e.g. in a floating div) that gives the
> user more information about the opt-back-in request.
> 
> 
Received on Wednesday, 25 January 2012 20:45:03 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:38:30 UTC