Opened 10 years ago
Closed 9 years ago
#5037 closed enhancement (invalid)
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)
Change History (6)
Changed 10 years ago by
| Attachment: | isSynthesized.patch added |
|---|
comment:1 Changed 9 years ago by
| Status: | new → open |
|---|
comment:2 Changed 9 years ago by
| Keywords: | needsreview added |
|---|---|
| Milestone: | 1.4 |
comment:3 follow-up: 4 Changed 9 years ago by
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 Changed 9 years ago by
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 9 years ago by
| Keywords: | needsreview removed |
|---|---|
| Priority: | minor → low |
| Resolution: | → invalid |
| Status: | open → closed |
Closed per request of the reporter.
Add isSynthesized member to event object. Patched against 1.3.2