- From: James Craig <jcraig@apple.com>
- Date: Wed, 20 Feb 2013 13:45:01 -0800
- To: Andy Heath <andyheath@axelrod.plus.com>
- Cc: Richard Schwerdtfeger <schwer@us.ibm.com>, Indie UI <public-indie-ui@w3.org>, Sangwhan Moon <smoon@opera.com>
On Feb 20, 2013, at 1:12 PM, Andy Heath <andyheath@axelrod.plus.com> wrote: > No - my meaning is that if the scope is as I understand you to be arguing for then the user context parts of the spec have no value as there"s no way to do anything useful that is not in existing practice without a mechanism to read prefs in, which we have justifiably set as out of scope for v1 . I'm not arguing that it should be in scope (I really don't think it should) - I *am* arguing we need to do *something* for interoperability otherwise I don't know why we are here. I expect something like might be be done with a browser extension, or perhaps a plist per taxonomy similar to a user style sheet, and therefore make it extensible so that third-party tools could augment the default preferences served by a mainstream browser. The specifics of how this would work however, are probably implementation details that are outside the scope of the spec. > Apols for typos - I can't read this iPad text properly as I need larger fonts ;-) :-) honestly Settings > General > Accessibility > Large Text ;-)
Received on Wednesday, 20 February 2013 21:45:34 UTC