EdgeHTML issue tracker

Report or search EdgeHTML issues, such as problems with site rendering or standards compliance. To request web platform features, visit the Microsoft Edge Platform Suggestion Box. If your issue is urgent, please contact Microsoft Support.

Issues

  • Missing CSS support for WebVTT subtitle styling (with ::cue pseudo-element)

    https://www.w3.org/TR/webvtt1/#the-cue-pseudo-element When using WebVTT subtitles, developers must use the ::cue pseudo-element to style them, such as allowing vision-impaired users to choose a

    4 reports
  • Implement WebVTT VTTCue region attribute

    Spec http://w3c.github.io/webvtt/#dom-vttcue-region Test http://w3c-test.org/webvtt/api/VTTCue/region.html This was implemented in Chromium in https://bugs.chromium.org/p/chromium/issues/detail?id=690014#c3

    1 report
  • Implement WebVTT VTTCue lineAlign and positionAlign attributes

    VTTCue.lineAlign and VTTCue.positionAlign are not supported. In the WebVTT syntax these are specified after a “,” in position and line settings. Spec: http://w3c.github.io/webvtt/#webvtt-cue-position-alignment

    2 reports
  • No support for the VTTCue interface

    The TextTrackCue interface is supported in IE10+ and Edge. However, this does not display 708 Captions (positioned closed captioned text) or HLS V4 subtitles with positioning information correctly.

    5 reports
  • Update web-platform-tests expectations for WebVTT parsing move

    See https://github.com/w3c/web-platform-tests/pull/5032 Reorganised tests: webvtt-file-format-parsing -> parsing, webvtt-file-parsing -> file-parsing and webvtt-cue-text-parsing-rules ->

    1 report
  • WebVTT rename "middle" to "center"

    The WebVTT spec changed align from ‘middle’ to ‘center’ to match CSS [1]. Compat analysis was done prior to the spec change [2]. [1] https://github.com/w3c/webvtt/pull/244 [2] https://github.com/w3c/webvtt/issues/301#issuecomment-224235961

    1 report
  • Spec change: A <track kind=invalid> should behave like metadata, not subtitles

    This is a deliberate change from preexisting behavior, see https://www.w3.org/2015/10/28-htmlcue-minutes.html https://github.com/whatwg/html/issues/293 Test https://github.com/w3c/web-platform-tests/pull/2941

    1 report
  • text tracks do not fire change, addtrack, or removetrack events

    URL: Repro Steps: create a page with a video element get a reference to the TextTrackList object from the video element attach change , addtrack , and removetrack listeners using both

    4 reports
  • TextTrackCue should not have a constructor

    URL: Repro Steps: http://jsconsole.com/?new%20TextTrackCue(0%2C%201%2C%20%27%27) Expected Results: new TextTrackCue(0, 1, ‘’) should throw an exception, but instead returns a new Actual Results:

    1 report
  • EME Compliance: Clear key misc - 25 Failures

    Edge 14953 fails the following W3C conformance test cases (tested using https://github.com/w3c/web-platform-tests/tree/master/encrypted-media ): Clear key misc - 25 Failures /encrypted-media/clearkey-mp4-reset-src-after-setmediakeys.html

    1 report
  • EME Compliance: Clear key persistent-license tests - 5 Failures

    Edge 14953 fails the following W3C conformance test cases (tested using https://github.com/w3c/web-platform-tests/tree/master/encrypted-media ): Clear key persistent-license tests - 5 Failures

    1 report
  • EME Compliance: requestMediaKeySystemAccess initData types

    requestMediaKeySystemAccess fails when provided with a mix of supported and unsupported initData types: The first line below succeeds, but the second line fails: navigator.requestMediaKeySystemAccess(

    1 report
  • EME Compliance: Clear key temporary - 18 Failures

    Edge 14953 fails the following W3C conformance test cases (tested using https://github.com/w3c/web-platform-tests/tree/master/encrypted-media ): Clear key temporary - 18 Failures /encrypted-media/clearkey-events-session-closed-event.html

    1 report
  • EME Compliance: DRM persistent-license failures - 5 Failures

    Edge 14953 fails the following W3C conformance test cases (tested using https://github.com/w3c/web-platform-tests/tree/master/encrypted-media ): DRM persistent-license failures - 5 Failures /encrypted-media/drm-mp4-playback-destroy-persistent-license.html

    1 report
  • EME Compliance: idlharness test failures

    Edge 14929 has the following problems with the idlharness test for Encrypted Media Extensions: Navigator interface: operation requestMediaKeySystemAccess(DOMString,[object Object]) – Property length

    1 report
  • EME does not track the label field

    When using navigator.requestMediaKeySystemAccess , the resulting object’s configuration does not include the label field. When calling getConfiguration on the result of the query, it should have

    2 reports
  • EME keyStatuses are missing methods

    In Edge, an EME session’s keyStatuses member is missing the methods keys(), values(), and entries(). For a quick demo, open the JS console and visit this page: http://storage.googleapis.com/shaka-demo-assets/_bugs/edge-eme-keystatus-iterator/index.html

    1 report
  • EME Compliance: DRM error handling - 24 Failures

    Edge 14953 fails the following W3C conformance test cases (tested using https://github.com/w3c/web-platform-tests/tree/master/encrypted-media ): DRM error handling - 24 Failures /encrypted-media/drm-events-session-closed-event.html

    1 report
  • EME Compliance: keyStatuses

    The Encrypted Media Extensions MediaKeySession keyStatuses attribute has the following problems in Microsoft Edge 25.10586.0.0: Symbol.iterator property is not present keys , values , and entries

    1 report
  • EME Compliance: persistent-usage-record

    Support for the persistent-usage-record session type has the following problems in Microsoft Edge 25.10586.0.0: the remove() method on a persistent-usage-record session that has been used for

    1 report

More in web platform