Bug 18531 - Support IE's function Test.prototype.bar() {} syntax
Summary: Support IE's function Test.prototype.bar() {} syntax
Status: RESOLVED DUPLICATE of bug 16997
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac OS X 10.5
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-16 08:59 PDT by Eric Seidel (no email)
Modified: 2011-08-09 11:56 PDT (History)
1 user (show)

See Also:


Attachments
test case (275 bytes, text/html)
2008-04-16 09:00 PDT, Eric Seidel (no email)
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Seidel (no email) 2008-04-16 08:59:19 PDT
Support IE's function Test.prototype.bar() {} syntax

It's very strange that this is allowed, but it seems to be.  See test case.  I've not tested deeper things like:
function Test.foo.bar.baz.prototype.foobar() {}

I'm unsure how many sites are affected by this.  I've seen it on at least one real site:
http://music.sogua.com/song/18103725.html#a1
Comment 1 Eric Seidel (no email) 2008-04-16 09:00:31 PDT
Created attachment 20585 [details]
test case
Comment 2 Gavin Barraclough 2011-08-08 15:44:26 PDT
This isn't widely supported and isn't on a standards track.  This is probably invalid/won't-fix.
Comment 3 Alexey Proskuryakov 2011-08-09 10:54:29 PDT
Is this related to bug 16997?
Comment 4 Gavin Barraclough 2011-08-09 11:56:21 PDT
(In reply to comment #3)
> Is this related to bug 16997?

Alexey,

Yes, yes it is. :-)

These are not on track for standardization, Firefox don't support these, and I think neither Chrome nor Opera do either?  Without interest from ECMA or wider browser support I don't think we'll want to adopt further proprietary and non-standard mechanisms, without a good reason.

A good reasons to reopen this bug would be ECMA adoption, wider de-facto support, or a major web compatibility issue.

*** This bug has been marked as a duplicate of bug 16997 ***