diff -r fdf0d272d74a encrypted-media/encrypted-media.html --- a/encrypted-media/encrypted-media.html Mon Jan 14 17:46:57 2013 -0800 +++ b/encrypted-media/encrypted-media.html Mon Jan 14 18:40:18 2013 -0800 @@ -324,7 +324,7 @@
  1. If type is null or an empty string and initData is not null or an empty string, throw an INVALID_ACCESS_ERR exception and abort these steps.

  2. -
  3. If type contains a MIME type that is not supported or is not supported by the keySystem, throw a NOT_SUPPORTED_ERR exception and abort these steps.

  4. +
  5. If type is not supported by the user agent and keySystem nor, throw a NOT_SUPPORTED_ERR exception and abort these steps. In most cases, this means type is not a supported media type.

  6. Let cdm be the cdm loaded in the MediaKeys constructor.

  7. @@ -338,19 +338,20 @@
  8. Add the new object to an internal list of session objects.

  9. -

    Schedule a task to generate a key request, providing type, initData, and the new object.

    +

    Schedule a task to complete initializion of the session, providing type, initData, and the new object. In most cases, this results in generation of a key request.

    The user agent will asynchronously execute the following steps in the task:

    1. Let defaultURL be null.

    2. -

      Use cdm to generate a key request and follow the steps for the first matching condition from the following list:

      +

      Use cdm to complete initializion and follow the steps for the first matching condition from the following list:

      -
      If a request is successfully generated
      +
      If the session is succesfully initialized
      1. -

        Let key request be a key request generated by the CDM using initData, if provided.

        +

        Let response be a message related to successful initialization.

        Note: cdm must not use any data, including media data, not provided via initData.

        +

        In most cases, this is a key request generated by the CDM using type and initData, if provided.

        type may be used to determine how to interpret initData.

      2. If initData is not null and contains a default URL for keySystem, let defaultURL be that URL.

      3. @@ -375,7 +376,7 @@

        queue a task to fire a simple event named keymessage at the new object

        The event is of type MediaKeyMessageEvent and has:

        Note: message may be a request for multiple keys, depending on the keySystem and/or initData. This is transparent to the application.

        diff -r fdf0d272d74a encrypted-media/encrypted-media.xml --- a/encrypted-media/encrypted-media.xml Mon Jan 14 17:46:57 2013 -0800 +++ b/encrypted-media/encrypted-media.xml Mon Jan 14 18:40:18 2013 -0800 @@ -317,7 +317,7 @@
        1. If type is null or an empty string and initData is not null or an empty string, throw an exception and abort these steps.

        2. -
        3. If type contains a MIME type that is not supported or is not supported by the keySystem, throw a exception and abort these steps.

        4. +
        5. If type is not supported by the user agent and keySystem nor, throw a exception and abort these steps. In most cases, this means type is not a supported media type.

        6. Let cdm be the cdm loaded in the MediaKeys constructor.

        7. @@ -330,17 +330,18 @@
        8. Add the new object to an internal list of session objects.

        9. -
        10. Schedule a task to generate a key request, providing type, initData, and the new object.

          +
        11. Schedule a task to complete initializion of the session, providing type, initData, and the new object. In most cases, this results in generation of a key request.

          The user agent will asynchronously execute the following steps in the task:

          1. Let defaultURL be null.

          2. -
          3. Use cdm to generate a key request and follow the steps for the first matching condition from the following list:

            +
          4. Use cdm to complete initializion and follow the steps for the first matching condition from the following list:

            -
            If a request is successfully generated
            +
            If the session is succesfully initialized
              -
            1. Let key request be a key request generated by the CDM using initData, if provided.

              +
            2. Let response be a message related to successful initialization.

              Note: cdm must not use any data, including media data, not provided via initData.

              +

              In most cases, this is a key request generated by the CDM using type and initData, if provided.

              type may be used to determine how to interpret initData.

            3. If initData is not null and contains a default URL for keySystem, let defaultURL be that URL.

            4. @@ -363,7 +364,7 @@
            5. to named keymessage at the new object

              The event is of type MediaKeyMessageEvent and has:

              • - message = key request

                + message = response

                destinationURL = defaultURL

              Note: message may be a request for multiple keys, depending on the keySystem and/or initData. This is transparent to the application.