ladybird/Userland/Libraries/LibWeb/UIEvents/MouseEvent.idl

// https://w3c.github.io/uievents/#mouseevent
[Exposed=Window, UseNewAKString]
interface MouseEvent : UIEvent {

    readonly attribute double offsetX;
    readonly attribute double offsetY;
    readonly attribute double clientX;
    readonly attribute double clientY;
    readonly attribute double screenX;
    readonly attribute double screenY;
    readonly attribute double x;
    readonly attribute double y;
    readonly attribute double pageX;
    readonly attribute double pageY;

    readonly attribute short button;
    readonly attribute unsigned short buttons;
};

dictionary MouseEventInit : EventModifierInit {

    // FIXME: offsetX and offsetY shouldn't be here.
    double offsetX = 0;
    double offsetY = 0;
    double clientX = 0;
    double clientY = 0;

    short button = 0;

};
LibWeb: Add Exposed attribute and IDL spec links where missing The intent is to use these to autogenerate prototype declarations for Window and WorkerGlobalScope classes. And the spec links are just nice to have :^) 2022-10-07 16:45:09 -06:00			`// https://w3c.github.io/uievents/#mouseevent`
LibWeb: Port {Mouse,UI,Wheel,}Event to new String This ports MouseEvent, UIEvent, WheelEvent, and Event to new String. They all had a dependency to T::create() in WebDriverConnection::fire_an_event() and therefore had to be ported in the same commit. 2023-04-06 16:12:33 +02:00			`[Exposed=Window, UseNewAKString]`
LibWeb: Change the parent interface of MouseEvent to UIEvent This was accidentally set to Event 2021-10-01 19:31:25 +03:00			`interface MouseEvent : UIEvent {`
LibWeb: Generate Event and MouseEvent bindings from IDL :^) We still have to hand-write a function to turn an Event& into a wrapper but this is still a hue improvement. Eventually we'll find a way to auto-generate that function as well. 2020-06-21 16:10:48 +02:00
			`readonly attribute double offsetX;`
			`readonly attribute double offsetY;`
LibWeb: Expose the MouseEvent::{clientX, clientY} attributes These provide the cursor coordinate within the viewport at which the event occurred (as opposed to the page relative coordinates exposed via offsetX, offsetY). 2021-04-15 20:50:02 +03:00			`readonly attribute double clientX;`
			`readonly attribute double clientY;`
LibWeb: Expose MouseEvent.{screenX,screenY} These are currently the same as clientX and clientY, but it works for now. 2022-11-05 14:40:31 +00:00			`readonly attribute double screenX;`
			`readonly attribute double screenY;`
LibWeb: Add MouseEvent.x and MouseEvent.y Per the CSSOM View spec, these are aliases for clientX and clientY. 2022-02-07 13:23:33 +01:00			`readonly attribute double x;`
			`readonly attribute double y;`
LibWeb: Support MouseEvent.{pageX,pageY} Unlike client{X,Y} which is relative to the current viewport, these offsets are relative to the left edge of the document (i.e they take scroll offset into account). 2022-12-31 16:40:36 +02:00			`readonly attribute double pageX;`
			`readonly attribute double pageY;`
LibWeb: Generate Event and MouseEvent bindings from IDL :^) We still have to hand-write a function to turn an Event& into a wrapper but this is still a hue improvement. Eventually we'll find a way to auto-generate that function as well. 2020-06-21 16:10:48 +02:00
LibWeb: Bring MouseEvent a bit closer to spec 2022-04-09 12:44:42 -03:00			`readonly attribute short button;`
LibWeb: Add button property in MouseEvent 2022-10-20 20:56:38 +03:00			`readonly attribute unsigned short buttons;`
LibWeb: Expect IDL namespace to end with semicolon From the Web IDL spec: https://heycam.github.io/webidl/#prod-Namespace Namespace :: namespace identifier { NamespaceMembers } ; 2020-12-09 21:26:42 +00:00			`};`
LibWeb: Bring MouseEvent a bit closer to spec 2022-04-09 12:44:42 -03:00
			`dictionary MouseEventInit : EventModifierInit {`

			`// FIXME: offsetX and offsetY shouldn't be here.`
			`double offsetX = 0;`
			`double offsetY = 0;`
			`double clientX = 0;`
			`double clientY = 0;`

			`short button = 0;`

LibWeb: Expose MouseEvent.{screenX,screenY} These are currently the same as clientX and clientY, but it works for now. 2022-11-05 14:40:31 +00:00			`};`