>> Although we did not discuss it in this week's meeting and thus did
>> not include this in my action item, I think it useful to convey that
>> a number of our WG members previously expressed that the privacy
>> issue raised, when considered in the larger context of DOM events, is
>> perhaps not very realistic. Input locale/keyboard would come in an
>> event that exposes information such as the IP address of the user,
>> their language preferences, cookies, and other identifying
>> information units that are probably better sources of fingerprinting
>> and profiling. Further, unlike many of these items, the "keyboard"
>> used can often be altered by the user (this message was typed with a
>> "Japanese input locale").
Indeed, there are currently many bits identifying a user. The question is
how many more bits we should add. Also, if the input locale is wildly
different from the actual text being written, the two purported use cases
(attractive quotes and text direction) will fail, if I understand things
correctly. Furthermore, there are some other mechanisms available today
that reveal the locale of the user to some extent (though not the keyboard
in use). Why would that not be sufficient?
--
Anne van Kesteren
http://annevankesteren.nl/