Implement object.readyState for HTML elements




12 years ago
2 days ago


(Reporter: sciguyryan, Unassigned)



Firefox Tracking Flags

(Not tracked)


(Whiteboard: [firebug-p3], URL)



12 years ago
Bug #347174 is a tracker for the implementation document.readyState. This bug will track implementation of object.readyState for some HTML objects as per support with IE (see the URL specified above).

Comment 1

11 years ago
Another important URL for considering this functionality is here, which describes the "onreadystatechange" event.

It may not seem entirely logical that a <table> element or an <input type="text"> would have a readyState at all, but I believe that the gist of what's happening here is that these elements (among others) may have a "datasrc" attribute in IE, and that's the "readyState" that is being reported here.

Also note that in Bug #347174 I report that the MSDN documentation appears to be wrong in places.  In particular, the supported elements for "readyState", "onReadyStateChange" and "dataSrc" look vaguely similar, but don't entirely overlap.

readyState applies to:
document, FRAME, IFRAME, IMG, INPUT type=button, INPUT type=checkbox, INPUT type=file, INPUT type=hidden, INPUT type=image, INPUT type=password, INPUT type=radio, INPUT type=reset, INPUT type=submit, INPUT type=text, LINK, SCRIPT, TABLE, TBODY, TD, TFOOT, TH, THEAD, TR

dataSrc applies to:
A, APPLET, BUTTON, DIV, FRAME, IFRAME, IMG, INPUT type=button, INPUT type=checkbox, INPUT type=hidden, INPUT type=image, INPUT type=password, INPUT type=radio, INPUT type=text, LABEL, MARQUEE, SELECT, SPAN, TABLE, TEXTAREA 

onreadystatechange applies to all elements (sort of):
"All elements expose an onreadystatechange event. The following objects always fire the event because they load data: applet, document, frame, frameSet, iframe, img, link, object, script, and xml elements. Other objects will only fire the onreadystatechange event when a DHTML Behavior is attached."
Whiteboard: [firebug-p3]
What is the usecase for these properties? Would the W3C standard Progress Events ( be a better option?
Assignee: general → nobody
QA Contact: ian → general
anything to do here? I think C#2 or using onReadyStateChange events is probably sufficient and more standards-compliant than emulating IE events.

Also, the linked URL in this bug has been moved.
I believe we established that implementing this isn't web-compatible?

Comment 5

2 days ago
Per policy at If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Last Resolved: 2 days ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.