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 19620 - Need definition of "next message" in addKey() procedure
Summary: Need definition of "next message" in addKey() procedure
Status: RESOLVED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: Encrypted Media Extensions (show other bugs)
Version: unspecified
Hardware: PC Windows 3.1
: P2 normal
Target Milestone: ---
Assignee: Adrian Bateman [MSFT]
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-19 07:09 UTC by Yang Sun
Modified: 2012-12-11 07:05 UTC (History)
3 users (show)

See Also:

Attachments

Description Yang Sun 2012-10-19 07:09:07 UTC 
In addKey() procedure, it is mentioned that if next message is not null, then fire keymessage to mediakeysession then to server.I do not quiet understand what is the "next message"? and what information will be delivered through keymessage at what scenario?
Comment 1 David Dorwin 2012-12-11 07:05:37 UTC 
"next message" is a variable, as indicated by the <var> markup and resulting italics font. If you read it as a variable, the algorithm describes exactly what it is and what to do with it.