This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 14089 - WF2: Caller on form doesn't appear to be supported in Opera/Mozilla/WebKit. Maybe it should be dropped. (Getter is supported though.)
Summary: WF2: Caller on form doesn't appear to be supported in Opera/Mozilla/WebKit. M...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-08 17:43 UTC by contributor
Modified: 2011-10-28 23:09 UTC (History)
12 users (show)

See Also:

Attachments

Description contributor 2011-09-08 17:43:08 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/complete/forms.html
Multipage: http://www.whatwg.org/C#the-form-element
Complete: http://www.whatwg.org/c#the-form-element

Comment:
Caller on form doesn't appear to be supported in Opera/Mozilla/WebKit. Maybe
it should be dropped. (Getter is supported though.)

Posted from: 85.227.153.57 by simonp@opera.com
User agent: Opera/9.80 (Macintosh; Intel Mac OS X 10.5.8; U; en) Presto/2.9.168 Version/11.51
Comment 1 Travis Leithead [MSFT] 2011-09-08 18:19:18 UTC 
IE9 looked at removing caller support (in our latest standards mode) for form element, but was unable to do so due to web compatibility. (Sorry, I don't have specific bugs/sites to cite.)

Even if the spec changes here, IE would be unable to implement this change unless it proves to no longer be a web compatibility issue.

I'd recommend keeping caller here.
Comment 2 Ms2ger 2011-10-23 13:11:28 UTC 
I'm pretty sure Mozilla will refuse to implement caller here (as elsewhere). If that causes compatibility issues for IE, I would recommend that Microsoft evangelizes the sites that use it.
Comment 3 Ian 'Hixie' Hickson 2011-10-25 05:10:58 UTC 
Input from WebKit and Opera wold be useful here.
Comment 4 Adam Barth 2011-10-26 07:03:26 UTC 
It's unlikely WebKit would add support for caller if we don't already have it.  It's just legacy nonsense.
Comment 5 Simon Pieters 2011-10-26 09:15:22 UTC 
Opera doesn't have plans to add caller here. (We might try to remove caller everywhere except document.all.)
Comment 6 Ian 'Hixie' Hickson 2011-10-28 23:08:18 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: see diff given below
Rationale: Since only one browser implements this and no other browser intends to implement this, I've removed it.

There are other places that have legacycaller also; I recommend following a similar approach (getting a majority of browser vendors to not support it and indicate a desire to continue not supporting it) if you would like those changed also.
Comment 7 contributor 2011-10-28 23:09:29 UTC 
Checked in as WHATWG revision r6781.
Check-in comment: compat with majority of browsers
http://html5.org/tools/web-apps-tracker?from=6780&to=6781