Closed
Bug 46046
Opened 26 years ago
Closed 26 years ago
load, error, abort events do not fire on INPUT image element
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P4)
Core
DOM: UI Events & Focus Handling
Tracking
()
People
(Reporter: jerone, Assigned: hjtoi-bugzilla)
References
Details
(Whiteboard: [nsbeta3+][PDTP4][fixinhand, see bug 22710])
Attachments
(2 files)
All javascript events for image are broken in mozilla
Javascript's image object does not support events on mozilla.
Reproducible: Always
Steps to Reproduce:
1.Load Attachment
2 [details] [diff].Preform each event listed
Actual Results: Nothing happens
Expected Results: An alert should pop up showing events name
OS tested on:Mac OS9,8.6, Win 98,2000,NT, & Linux redhat 6.0
BuildID: 2000-07-1911-m17
| Assignee | ||
Comment 3•26 years ago
|
||
keypress, keyup, keydown events should not work for non-focusable content, see
bug 46042.
(build 2000072520) onkeyup, onkeydown, onkeypress cause an alert to pop up;
this can be reproduced by
1. loading the attachment
2 [details] [diff] [review]. clicking on the top image
3. hitting the TAB key repeatedly
I can't think of any way to get the onerror action to be called;
it seems that the onload event isn't working.
Re: Heikki's comment; this is focusable content. This bug (at least the
attachment) refers only to
<INPUT TYPE='IMAGE'>, not a general image object
Status: UNCONFIRMED → NEW
Ever confirmed: true
| Assignee | ||
Comment 5•26 years ago
|
||
Right, I can get the key events like you described and yes, they should happen
for input element.
Regarding the onload: I believe jst@netscape.com has some bug on his plate about
onload not working. But maybe it was about the whole document...
Comment 6•26 years ago
|
||
Mass update: changing qacontact to ckritzer@netscape.com
QA Contact: janc → ckritzer
| Assignee | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
| Assignee | ||
Comment 9•26 years ago
|
||
Per discusion with Nisheeth, marking nsbeta3+. Will email ekrock to verify.
Whiteboard: [nsbeta3+]
| Assignee | ||
Updated•26 years ago
|
Priority: P3 → P2
| Assignee | ||
Comment 10•26 years ago
|
||
Hmm... Strictly speaking there is no spec out there (that I am aware of) that
defines these attributes for INPUT element. HTML4 doesn't, and DOM does not
define attributes. JS (at developer.netscape.com) comes close when it defines
onAbort, onError and onLoad for IMG element. I'd assume INPUT is omitted because
at the time the docs were written INPUT could not have image type content. In
any case, they don't work for IMG element either (bug 22710).
Anyway, IE 5 kicks at least the onerror handler because it cannot find the
image.
Comment 11•26 years ago
|
||
Once bug 28277 is fixed this should be easier to fix, the problem right now is
that the HTMLImageElement doesn't register a callback to the image loader and
thus it never knows when the image has loaded. Once a callback is in place the
fireing of the events could be added to the same callback...
Depends on: 28277
| Assignee | ||
Comment 12•26 years ago
|
||
Changing summary. Was "Events don't work on Javascript image object"
Summary: Events don't work on Javascript image object → load, error, abort events do not fire on INPUT image element
Comment 13•26 years ago
|
||
PDT thinks this could be demoted to p4 because image inputs are pretty rare
Priority: P2 → P4
Whiteboard: [nsbeta3+] → [nsbeta3+][PDTP4]
| Assignee | ||
Comment 14•26 years ago
|
||
| Assignee | ||
Updated•26 years ago
|
Whiteboard: [nsbeta3+][PDTP4] → [nsbeta3+][PDTP4][fixinhand, see bug 22710]
| Assignee | ||
Comment 15•26 years ago
|
||
I am marking this bug dup, because the fix to 22710 is going to fix this as
well. This was suspected all along, but this bug was kept open just in case.
*** This bug has been marked as a duplicate of 22710 ***
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
Comment 16•25 years ago
|
||
Marking VERIFIED DUPLICATE on:
- LinuxRH62 2000-09-13-08-M18 Commercial
- Win98 2000-09-13-08-M18 Mozilla
- MacOS86 2000-09-13-04-M18 Commercial
Status: RESOLVED → VERIFIED
Updated•7 years ago
|
Component: Event Handling → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•