Re: Regarding issue issue #376

David,
I don’t think that is an option for us. Michael may be able to say otherwise, but in general it is unwise to reference an definition from a non-REC-document because even if we think that it is unlikely to change, it could.

@patricklauke – when is the updated Rec expected?

Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe

akirkpat@adobe.com
http://twitter.com/awkawk


From: David MacDonald <david100@sympatico.ca<mailto:david100@sympatico.ca>>
Date: Friday, September 15, 2017 at 06:12
To: WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Subject: Regarding issue issue #376
Resent-From: WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Resent-Date: Friday, September 15, 2017 at 06:13

I've reviewed the comment which is asking the group to consider having one definition of pointer events rather than having references to the first version of pointer events any other definition point to the second. Patrick explained that the new pointer events version is in first public working draft. And if it's possible to reference that, given that it's moving towards full acceptance, that would be preferable.

I agree with that sentiment. I don't see any logistical reason why we can't reference the latest definition, as long as it's consistent and will not change. I think even if it undergoes minor changes there's very little risk of it becoming a problem for our definition of pointer events.

I would like to propose that we reference the latest version of pointer events for all references, and close the issue.


Cheers,
David MacDonald



CanAdapt Solutions Inc.

Tel:  613.235.4902

LinkedIn
<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linkedin.com%2Fin%2Fdavidmacdonald100&data=02%7C01%7C%7Cf966ad5e48794ab5d82908d4fc227b89%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636410672413140393&sdata=GLzlaxT7nA7vPBQTnSj9b3p8mSKgig3su%2Bbc5xtIzvo%3D&reserved=0>

twitter.com/davidmacd<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fdavidmacd&data=02%7C01%7C%7Cf966ad5e48794ab5d82908d4fc227b89%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636410672413140393&sdata=6uz2OAJ6dR9IYAVLjL6qiV%2BJe0OYnn0G1Y4mMT3zZik%3D&reserved=0>

GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FDavidMacDonald&data=02%7C01%7C%7Cf966ad5e48794ab5d82908d4fc227b89%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636410672413140393&sdata=vkJiLEaQkyURK%2Be9nopgykLAq59s80j44TwKIbpP01o%3D&reserved=0>

www.Can-Adapt.com<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.can-adapt.com%2F&data=02%7C01%7C%7Cf966ad5e48794ab5d82908d4fc227b89%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636410672413140393&sdata=Tp1286QjDHZkzOEx%2BiByskScK1eOnVoq%2BxOd%2BpTUEm8%3D&reserved=0>



  Adapting the web to all users

            Including those with disabilities

If you are not the intended recipient, please review our privacy policy<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.davidmacd.com%2Fdisclaimer.html&data=02%7C01%7C%7Cf966ad5e48794ab5d82908d4fc227b89%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636410672413140393&sdata=4uMZThm2INmYv6bsBo7nuLAwCCqTOIY8ihbVbdKPIhM%3D&reserved=0>