Bug Tracker

Modify

Ticket #5037 (closed enhancement: invalid)

Opened 5 years ago

Last modified 3 years ago

Distinguish synthesized events

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

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

isSynthesized.patch Download (841 bytes) - added by happygiraffe 5 years ago.
Add isSynthesized member to event object. Patched against 1.3.2

Change History

Changed 5 years ago by happygiraffe

Add isSynthesized member to event object. Patched against 1.3.2

comment:1 Changed 3 years ago by dmethvin

  • Status changed from new to open

comment:2 Changed 3 years ago by dmethvin

  • Keywords needsreview added
  • Milestone 1.4 deleted

comment:3 follow-up: ↓ 4 Changed 3 years ago by 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?

comment:4 in reply to: ↑ 3 Changed 3 years ago by happygiraffe

Replying to 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.

comment:5 Changed 3 years ago by jitter

  • Keywords needsreview removed
  • Priority changed from minor to low
  • Status changed from open to closed
  • Resolution set to invalid

Closed per request of the reporter.

Please follow the  bug reporting guidlines and use  jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.

View

Add a comment

Modify Ticket

Action
as closed
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.