Bug 7928

Summary:

Autogenerate UIEvent, MouseEvent and KeyboardEvent

Product:

WebKit

Reporter:

Eric Seidel (no email) <eric>

Component:

WebKit Misc.

Assignee:

Eric Seidel (no email) <eric>

Status:

RESOLVED FIXED

Severity:

Normal

Priority:

Version:

420+

Hardware:

Mac

OS:

OS X 10.4

Attachments:

Description	Flags
Incomplete first attempt at autogenerating UIEvent, MouseEvent & KeyboardEvent	darin: review-

Eric Seidel (no email)

Reported 2006-03-23 03:08:15 PST

Autogenerate UIEvent, MouseEvent and KeyboardEvent I decided it was time to get my hands dirty with the autogenerated bindings...

Attachments
Incomplete first attempt at autogenerating UIEvent, MouseEvent & KeyboardEvent (48.94 KB, patch) 2006-03-23 03:18 PST, Eric Seidel (no email)	darin: review-	Details Formatted Diff Diff
View All Add attachment proposed patch, testcase, etc.

Eric Seidel (no email)

Comment 1 2006-03-23 03:18:48 PST

Created attachment 7248 [details] Incomplete first attempt at autogenerating UIEvent, MouseEvent & KeyboardEvent I'm marking this patch for review even though I know it is incomplete. Currently it doesn't properly handle marking of the clipboard object on MouseEvent when MouseEvent is marked. There are probably other things it doesn't quite do right too. I'm posting this for review now so that we can hash out the details all having looked at the same patch. I also think that this code will need at least one test case which tries to dispatch to a DocType node or something else which is a node but not an EventTarget.

Darin Adler

Comment 2 2006-03-23 07:19:07 PST

Anders said he had already completed the event classes, so you might want to talk to him about it. In cases like mouse event where you have something custom to do, you need to create a base class that is hand-written to go along with the autogenerated code.

Darin Adler

Comment 3 2006-03-24 08:24:01 PST

Comment on attachment 7248 [details] Incomplete first attempt at autogenerating UIEvent, MouseEvent & KeyboardEvent Either we have to mark the clipboard or prove that we don't need to mark it -- I'd like to see a test that explores this. Patch otherwise looks fine to me.

Eric Seidel (no email)

Comment 4 2006-03-28 14:57:50 PST

(In reply to comment #3) > (From update of attachment 7248 [details] [edit]) > Either we have to mark the clipboard or prove that we don't need to mark it -- > I'd like to see a test that explores this. I'm not even sure what clipboard is used for. It looks like it's used during Dragging and Clipboard events, but only seems to be marked when dragging. I've moved that code down onto DOMEvent, as that is where the clipboard pointer was being stored anyway. > Patch otherwise looks fine to me. >

Eric Seidel (no email)

Comment 5 2006-04-14 18:00:28 PDT

This has been since fixed and landed.

Note You need to log in before you can comment on or make changes to this bug.