Re: Identify Common Purpose - resolving issues

HI Mike,



Two replies:



> we seem to have lost the wording that these items are user-specific.



The paragraph at the top of the list clarifies the purpose is user-specific, Jake & I didn’t think it needed to be in both places. If we referred to HTML5 directly, we would need it in the SC but otherwise I think it’s redundant.





> … In both situations, if the autofill information changes in HTML 5.3, particularly if a value is removed, what are authors to do?



I think that’s unlikely, and the process would be very slow given that browsers have to change their implementations as well. Presumably an author could use an attribute that has been removed from HTML, it will probably work for a while. If it is removed from browsers quickly, it just wouldn’t do anything unless the user had an extension that made use of it.

Could that be dealt with using accessibility supported? Hmm, not sure that’s granular enough. But, as you said:



> I can live with the assumption we'll 'fix it' in some way if/when that arises.



Cheers,



-Alastair

Received on Wednesday, 17 January 2018 15:48:14 UTC