EME MediaKeyStatusMap forEach argument order is backward

Issue #8052410 • Assigned to Gurpreet V.

Details

Author
Joey P.
Created
Jun 30, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

Latest EME spec says that MediaKeyStatusMap forEach should pass the status first, then the key ID. Edge currently has this backward.

  1. Visit https://storage.googleapis.com/shaka-demo-assets/_bugs/eme-foreach/index.html
  2. Open JS console
  3. You will see “forEach order is correct” or “forEach order is backward”

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Ibrahim O.”

      Changed Assigned To to “Venkat K.”

      Changed Assigned To from “Venkat K.” to “Nishant N.”

      Changed Assigned To from “Nishant N.” to “Shawn P.”

      Changed Assigned To from “Shawn P.” to “Gurpreet V.”

      Changed Status to “Not reproducible”

    • Still reproducible with Edge/16.16299.

      @Gurpreet, can you be more specific when you set status to "not reproducible"? Not reproducible with which version of Edge? When can developers expect to see this fix?

    • Changed Status from “Not reproducible”

    • Reopening the issue. Please give some details about the version in which this issue is fixed.

    • Microsoft Edge Team

      Changed Assigned To to “Gurpreet V.”

    You need to sign in to your Microsoft account to add a comment.

    Sign in