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 25627 - Indicate that Key objects have internal state, and that the attributes they expose are reflections of that internal state
Summary: Indicate that Key objects have internal state, and that the attributes they e...
Status: RESOLVED FIXED
Alias: None
Product: Web Cryptography
Classification: Unclassified
Component: Web Cryptography API Document (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Ryan Sleevi
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-09 00:41 UTC by Ryan Sleevi
Modified: 2014-06-16 23:17 UTC (History)
2 users (show)

See Also:

Attachments

Description Ryan Sleevi 2014-05-09 00:41:46 UTC 
Raised during the W3C TAG review ( https://github.com/w3ctag/spec-reviews/issues/3 )

The current specification language uses language-violating concepts like describing how to "set" readonly attributes of interfaces.

Instead of this, the TAG-preferred method is to notate that interfaces, such as Key, have internal attributes that mirror their external names - eg: [[algorithm]], [[type]], etc.

Accessing the attribute "algorithm" will return the value of the internal attribute [[algorithm]]

See, for example, the proposed language in https://github.com/w3ctag/spec-reviews/issues/3#issuecomment-42093558