Re: ISSUE-4 and clarity regarding browser defaults

Yes, but the sense I'm getting is that the current spec sacrifices a 
great deal in certainty in ways that can get very simply taken care of 
by requiring UAs to get a user election.

That wouldn't really be overly prescriptive. UAs, plugins, etc., will 
have a great deal of leeway in how to go about doing this, when, etc.

On 6/21/2012 12:45 AM, Rob van Eijk wrote:
> Because an overly prescriptive objective will not leave room for other 
> ways to accomplish the same.
> In order to have a meaningful global DNT standard, it is important to 
> have technical building blocks built in.
> On 20-6-2012 20:34, Tamir Israel wrote:
>> If the WG's objective is to ensure user preferences are expressed, 
>> why don't we simply make this a MUST?
>> On 6/20/2012 10:15 PM, Rob van Eijk wrote:
>>> Tnx Roy,
>>> Normative: "... users MAY be given a choice during installation, 
>>> update or first startup."
>>> Non-normative:
>>> There are use cases, where a choice given on first startup would be 
>>> the preferred choice mechanism.
>>> For example,
>>> - a device can have multiple user profiles per installation;
>>> - in cases where browsers are not installed by the user.
>>> Rob
>>> On 20-6-2012 18:22, Roy T. Fielding wrote:
>>>> On Jun 20, 2012, at 5:31 PM, Rob van Eijk wrote:
>>>>> "... users may be given a choice during installation, update or 
>>>>> first startup."
>>>> Not during installation or update -- only during first use.
>>>> The preference should be stored in the user's browser config (along
>>>> with their other personal preferences); a device might want
>>>> to have multiple such user profiles per installation.
>>>> In normal enterprise environments and the vast majority of purchased
>>>> computers, browsers are not installed by the user.  They are installed
>>>> by sysadmins, vendors, etc.  Likewise, updates should not modify
>>>> user preferences.
>>>> ....Roy

Received on Thursday, 21 June 2012 04:51:22 UTC