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 18681 - Should make sure any interface with a caller doesn't support legacycaller
Summary: Should make sure any interface with a caller doesn't support legacycaller
Status: NEW
Alias: None
Product: HTML WG
Classification: Unclassified
Component: testsuite (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-24 19:15 UTC by Ian 'Hixie' Hickson
Modified: 2012-08-28 13:48 UTC (History)
7 users (show)

See Also:

Attachments

Description Ian 'Hixie' Hickson 2012-08-24 19:15:41 UTC 
Historically, many browsers have implemented "legacycaller" for interfaces with a "getter". We should make sure that all the interfaces that _don't_ have a legacycaller don't support being invoked as functions, especially those that have a "getter".
Comment 1 James Graham 2012-08-25 09:43:41 UTC 
Sounds like something to add to idlharness.js
Comment 2 Ms2ger 2012-08-25 10:08:41 UTC 
Robin, does your WebIDL parser already support legacycaller?
Comment 3 Robin Berjon 2012-08-28 13:48:39 UTC 
(In reply to comment #2)
> Robin, does your WebIDL parser already support legacycaller?

Not unless someone has patched it in recently. I hope to be able to bring that code completely up to date in the reasonably close future.