[Bug 24095] MouseEvent and TouchEvent co-ordinate types should be kept in-sync

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24095

--- Comment #1 from Simon Pieters <simonp@opera.com> ---
Currently http://dvcs.w3.org/hg/webevents/raw-file/v1/touchevents.html has:
[[
partial interface Document {
    Touch     createTouch (WindowProxy view, EventTarget target, long
identifier, long pageX, long pageY, long screenX, long screenY);
    TouchList createTouchList (Touch... touches);
};

interface Touch {
    readonly    attribute long        identifier;
    readonly    attribute EventTarget target;
    readonly    attribute long        screenX;
    readonly    attribute long        screenY;
    readonly    attribute long        clientX;
    readonly    attribute long        clientY;
    readonly    attribute long        pageX;
    readonly    attribute long        pageY;
};
]]

The proposal is to change it to:

[[
partial interface Document {
    Touch     createTouch (WindowProxy view, EventTarget target, long
identifier, double pageX, double pageY, double screenX, double screenY);
    TouchList createTouchList (Touch... touches);
};

interface Touch {
    readonly    attribute long        identifier;
    readonly    attribute EventTarget target;
    readonly    attribute double        screenX;
    readonly    attribute double        screenY;
    readonly    attribute double        clientX;
    readonly    attribute double        clientY;
    readonly    attribute double        pageX;
    readonly    attribute double        pageY;
};
]]

?

What about pageX/pageY/x/y/offsetX/offsetY? What about using a constructor for
Touch with a TouchInit dict instead of (or in addition to) a factory function?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 9 April 2014 08:12:49 UTC