[Webkit-unassigned] [Bug 68002] New: Some interface attributes do not appear on the prototype as required by WebIDL
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Tue Sep 13 07:03:13 PDT 2011
https://bugs.webkit.org/show_bug.cgi?id=68002
Summary: Some interface attributes do not appear on the
prototype as required by WebIDL
Product: WebKit
Version: 528+ (Nightly build)
Platform: All
URL: http://dev.w3.org/2006/webapi/WebIDL/#es-attributes
OS/Version: All
Status: UNCONFIRMED
Severity: Major
Priority: P2
Component: New Bugs
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: webkit at martintribe.org
CC: yutak at chromium.org
I was attempting to object detect support for binary type support in the WebSocket object and discovered that the binaryType attribute is not visible in the prototype (https://bugs.webkit.org/show_bug.cgi?id=67335#add_comment). For WebSocket object detection this is a blocking issue because instantiating the object triggers a network connection (even if you immediately call close() and null the websocket object in the same execution context).
However, it seems like a more general issue of efficiency (object detection without needing instantiantion) and also of compliance with the WebIDL definition of attributes: http://dev.w3.org/2006/webapi/WebIDL/#es-attributes:
"For each attribute defined on the interface, there must exist a corresponding property. If the attribute was declared with the [Unforgeable] extended attribute, then the property exists on every object that implements the interface. Otherwise, it exists on the interface’s interface prototype object."
I'm not sure how widely this problem exists Chrome, but at least for WebSocket attributes, firefox and opera are correct and have the attributes names visible on the prototype.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list