LGTM1

/Daniel

On 2024-06-26 20:16, 'Sahir Vellani' via blink-dev wrote:
The PR is ready and has been *approved *by the PEWG.

The shape of the API has been reverted to an id (albeit with a slight name change, persistentDeviceId) on the main PointerEvent interface. All links along with request for positions have been updated. Linking the spec pr here <https://github.com/w3c/pointerevents/pull/495>for convenience.

On Thursday, May 23, 2024 at 7:00:38 AM UTC-7 fla...@chromium.org wrote:

    There were some fresh concerns raised about the shape of the spec
    PR <https://github.com/w3c/pointerevents/pull/495> which are being
    hashed out on that review thread. I will give it approval once we
    reach a consensus there.

    On Wed, May 22, 2024 at 4:30 PM Yoav Weiss (@Shopify)
    <yoav...@chromium.org> wrote:

        OK, thanks for outlining the spec mechanics :)

        Regardless of whether the PR actually lands in the spec, for
        the purpose of risk-assessment, it's even more interesting to
        know if the PR is *ready* to land in the spec.
        Can y'all clarify its review status? If it's ready to land,
        can a spec editor approve it, even if it doesn't land until later?

        On Fri, May 17, 2024 at 10:18 AM Patrick H. Lauke
        <re...@splintered.co.uk> wrote:



            On 16/05/2024 21:05, Robert Flack wrote:
            > I believe the reason for waiting is that the intention
            is to switch to a
            > different publishing model after level 3 is published?
            @Patrick H. Lauke
            > <mailto:re...@splintered.co.uk> to confirm.

            Apologies for the convoluted model here ... I have to
            admit that I'm
            actually not sure what the expected way of working around
            this is, as
            Pointer Events has been such a "slow and steady" process
            so far, with a
            very linear way of working - it's only now that we're just
            hoping to get
            PE3 to REC and then had this extra functionality come in
            that we've hit
            this snag. I will check with Philippe at W3C to work out
            what the best
            way forward here is (have the "frozen" version that makes
            its way
            through the steps to REC, while being able to already have a
            "future/next" branch).

            P
-- Patrick H. Lauke

            * https://www.splintered.co.uk/
            * https://github.com/patrickhlauke
            * https://flickr.com/photos/redux/
            * https://mastodon.social/@patrick_h_lauke

--
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/98e62b43-af6b-4db6-a6b7-b76bc0864eedn%40chromium.org <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/98e62b43-af6b-4db6-a6b7-b76bc0864eedn%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/619d8f4a-54ef-4b0b-8e02-869cc455bb16%40sarasas.se.

Reply via email to