W3C home > Mailing lists > Public > public-pointer-events@w3.org > January to March 2014

[Bug 24777] New: Add tiny note to 11.2 - list item nr 2 (mousemove) to clarify the reason for it

From: <bugzilla@jessica.w3.org>
Date: Sat, 22 Feb 2014 20:55:28 +0000
To: public-pointer-events@w3.org
Message-ID: <bug-24777-5978@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24777

            Bug ID: 24777
           Summary: Add tiny note to 11.2 - list item nr 2 (mousemove) to
                    clarify the reason for it
           Product: PointerEventsWG
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Pointer Events specification
          Assignee: jrossi@microsoft.com
          Reporter: redux@splintered.co.uk
        QA Contact: public-pointer-events-bugzilla@w3.org
                CC: public-pointer-events@w3.org

Currently 11.2 item 2 reads:

"If the pointer event to be dispatched is pointerover and the pointerdown event
has not yet been dispatched for this pointer, then fire a mousemove event."

I wonder if it's worth adding a tiny clarification right at the end, to explain
that this is done purely for compatibility (I usually call this a "sacrificial"
mousemove when talking about touch events' mouse compat)

"If the pointer event to be dispatched is pointerover and the pointerdown event
has not yet been dispatched for this pointer, then fire a mousemove event (for
compatibility with legacy mouse-specific script)" or similar?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Saturday, 22 February 2014 20:55:30 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:20:26 UTC