JDK-7063739 : FF: applet.status has ambiguous type
  • Type: Bug
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 7-client
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2011-07-07
  • Updated: 2011-09-22
  • Resolved: 2011-09-06
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availabitlity Release.

To download the current JDK release, click here.
7u2 b04Fixed 8Fixed
window.alert(applet.status) reports "class NPObject Ambiguous member class" in the Firefox.
Works ok (reports number) in IE

applet.status() reports number in FF.

Would be good to improve field access.

EVALUATION I guess that's because it treated it as method. I have being advocate we should implement status as read-only property, not method. That is, don't support applet.status().

EVALUATION Ambiguos class is reported because we define both property and method functions on "status" object. This is probably ok. But may be we can improve default conversion logic to return value instead of type? I.e. why would window.alert(applet.status) show type and not number?