- From: Tamir Israel <tisrael@cippic.ca>
- Date: Wed, 20 Jun 2012 23:34:38 -0400
- To: rob@blaeu.com
- CC: "Roy T. Fielding" <fielding@gbiv.com>, Rigo Wenning <rigo@w3.org>, Matthias Schunter <mts-std@schunter.org>, "publ >> \"public-tracking@w3.org\"" <public-tracking@w3.org>
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, > > <PROPOSED CHANGE> > 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. > </PROPOSED CHANGE> > > Rob > > On 20-6-2012 18:22, Roy T. Fielding wrote: >> On Jun 20, 2012, at 5:31 PM, Rob van Eijk wrote: >> >>> <PROPOSED CHANGE> >>> "... users may be given a choice during installation, update or >>> first startup." >>> </PROPOSED CHANGE> >> 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 03:36:14 UTC