>From my understanding, we need to wait for the PointerEvents spec V3 to be 
published before the PR can be merged; this change is slated for the 4th 
iteration of the spec.

On Wednesday, May 15, 2024 at 9:02:52 AM UTC-7 Chris Harrelson wrote:

> Hi,
>
> I see the spec PR is still pending. Is there a reason it can't land before 
> shipping?
>
> On Thu, May 9, 2024 at 12:23 PM 'Sahir Vellani' via blink-dev <
> blin...@chromium.org> wrote:
>
>> Done! I've updated the explainer as well as the links in the TAG review.
>>
>> On Thursday, May 9, 2024 at 8:51:02 AM UTC-7 jyas...@chromium.org wrote:
>>
>>> Oops, Ben's not at Microsoft anymore, so you've done the best you can 
>>> with the Mozilla and WebKit position requests. Thanks.
>>>
>>> On Thu, May 9, 2024 at 8:48 AM Jeffrey Yasskin <jyas...@chromium.org> 
>>> wrote:
>>>
>>>> If you've moved the explainer, could you replace the content of 
>>>> https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/PointerEventDeviceId/explainer.md
>>>>  
>>>> with a pointer to the new location? Then people who follow the old links 
>>>> won't be confused. You can and should also update the links in 
>>>> https://github.com/w3ctag/design-reviews/issues/880, and @Ben Mathwig 
>>>> should 
>>>> update the links in 
>>>> https://github.com/mozilla/standards-positions/issues/715 and 
>>>> https://github.com/WebKit/standards-positions/issues/102.
>>>>
>>>> Thanks,
>>>> Jeffrey
>>>>
>>>> On Wed, May 8, 2024 at 7:14 PM 'Sahir Vellani' via blink-dev <
>>>> blin...@chromium.org> wrote:
>>>>
>>>>> I've published the spec PR. Since I can't update the links in the 
>>>>> original comment of this thread, I'd like to link the updated explainer 
>>>>> here for visibility.  
>>>>> pointer-event-extensions/pointer-event-device-id-explainer.md 
>>>>> at main · WICG/pointer-event-extensions (github.com) 
>>>>> <https://github.com/WICG/pointer-event-extensions/blob/main/pointer-event-device-id-explainer.md>
>>>>> I have added comments to both request-for-positions informing of the 
>>>>> changes to the API. 
>>>>> Thanks for your comments Dan!
>>>>>
>>>>> On Wednesday, May 8, 2024 at 6:10:48 PM UTC-7 dan...@microsoft.com 
>>>>> wrote:
>>>>>
>>>>>> A non-blocking comment: now that the syntax has been changed I think 
>>>>>> it would be great if you could update the Explainer and the Mozilla and 
>>>>>> WebKit requests-for-position to reduce potential for confusion.
>>>>>>
>>>>>> Also, is there a reason the spec PR is still in Draft status? Could 
>>>>>> it be published so that there's no ambiguity for reviewers that this is 
>>>>>> (hopefully) moving forward imminently?
>>>>>>
>>>>>> -- Dan
>>>>>>
>>>>>> On Wednesday, May 8, 2024 at 2:00:38 PM UTC-7 sahir.vellani via 
>>>>>> Chromestatus wrote:
>>>>>>
>>>>>>> This is ready for another review :)
>>>>>>>
>>>>>> -- 
>>>>> You received this message because you are subscribed to the Google 
>>>>> Groups "blink-dev" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>>> an email to blink-dev+...@chromium.org.
>>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/52090dcd-f068-456d-be41-bfadbb9055d1n%40chromium.org
>>>>>  
>>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/52090dcd-f068-456d-be41-bfadbb9055d1n%40chromium.org?utm_medium=email&utm_source=footer>
>>>>> .
>>>>>
>>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "blink-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to blink-dev+...@chromium.org.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6034517b-2f18-4f57-b36c-dc58cdce99afn%40chromium.org
>>  
>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6034517b-2f18-4f57-b36c-dc58cdce99afn%40chromium.org?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/2d87b3da-9f3d-4c72-a45e-dff1e5cdcb81n%40chromium.org.

Reply via email to