Bug Tracker

#5037 closed enhancement (invalid)

Opened August 12, 2009 10:37AM UTC

Closed November 24, 2010 11:15AM UTC

Distinguish synthesized events

Reported by: happygiraffe Owned by: brandon
Priority: low Milestone:
Component: event Version: 1.3.2
Keywords: Cc:
Blocked by: Blocking:
Description

It would be very useful if we could distinguish events which are synthesized. My use case is that I want to call click() on a page load, but that's setting the focus, which moves the viewport away from the anchor location. I've changed my code to check for the presence of a button in the event, but I feel it would be useful to have an isSynthesized property in the event object.

Attachments (1)
  • isSynthesized.patch (0.8 KB) - added by happygiraffe August 12, 2009 10:38AM UTC.

    Add isSynthesized member to event object. Patched against 1.3.2

Change History (5)

Changed November 18, 2010 04:10AM UTC by dmethvin comment:1

status: new → open

Changed November 18, 2010 04:11AM UTC by dmethvin comment:2

keywords: → needsreview
milestone: 1.4

Changed November 23, 2010 01:17AM UTC by snover comment:3

Isn’t dispatching fake events for their side-effects considered an anti-pattern, and isn’t the only purpose of this feature request to make it possible to more easily exploit this pattern?

Changed November 24, 2010 10:23AM UTC by happygiraffe comment:4

Replying to [comment:3 snover]:

Isn’t dispatching fake events for their side-effects considered an anti-pattern, and isn’t the only purpose of this feature request to make it possible to more easily exploit this pattern?

Unfortunately, I can't remember the original context that caused me to file this bug. As I can't find a good reason, I'm happy for it to be closed.

Changed November 24, 2010 11:15AM UTC by jitter comment:5

keywords: needsreview
priority: minor → low
resolution: → invalid
status: open → closed

Closed per request of the reporter.