https://wicg.github.io/picture-in-picture/

Hello
The site (https://play.sfr.fr/) is not compatible with EDGE !
Please, please, please, fix it (CSS, HTML, JavaScript, etc.)

The built-in PDF viewer displays a noise pattern when attempting to view black/white images encoded as JBIG2. A lot of scanners produce files in this format for black/white scans, and all other PDF viewers seem to handle the format fine.

Happy to provide a sample file if required.

Hello,
it seems that ORTC/WebRTC stack does not add VP8 RTP PictureID [1] which is needed by Switching Mixer Media Servers [2] to properly perform its rewriting when RTP flow switchings take place in order to avoid some issues in clients (eg: Chrome) that depend on it.

Could it be added as feature request?

Thanks in advance!!

Refs
[1] https://tools.ietf.org/html/rfc7741#section-4.2
[2] https://tools.ietf.org/html/rfc7667#section-3.6.2

Microsoft Edge does not support page linking in internal PDF viewer.

In Chrome and Firefox you can jump straight to a page with a URL Hashtag suffix.

For example, to jump straight to page 9 of this Microsoft PDF, adding "#page=9" will take you directly there in Chrome/Firefox.

http://abouttmc.com/wp-content/uploads/2016/10/Dynamics-365-for-Financials-Capabilities-Guide-TMC-2016-11.pdf#page=9

However Microsoft Edge does not support this feature.

As a **developer**, I have pages coded to link to specific pages in PDFs that are up to 1,300 pages long... this is really frustrating for our end users.

The ssrc-audio-level RTP header extension is missing from
ORTC and WebRTC..
urn:ietf:params:rtp-hdrext:ssrc-audio-level

Relevant links:
https://www.w3.org/TR/webrtc-stats/#dom-rtcmediastreamtrackstats
https://tools.ietf.org/html/rfc6464
https://webrtchacks.com/wp-content/themes/parament/custom-pages/sdp/24.html
https://www.w3.org/TR/webrtc-stats/#dom-rtcmediastreamtrackstats

Also submitted here:
https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/14540865/

very useful feature for the browser

https://simpl.info/videoalpha/
https://developers.google.com/web/updates/2013/07/Alpha-transparency-in-Chrome-video
https://bugzilla.mozilla.org/show_bug.cgi?id=944117

Chrome and Firefox support alpha transparency for VP8/9 but Edge does not. Please support this.

I have this problem where Edge does not render the Ravie font in a shown PDF file (the text in that font just does not show up!). In Chrome, IE, Adobe Reader etc. etc. it all works correctly ...

Add support for FLIF, the Free Lossless Image Format! Its benefits include progressive enhancement, transparency, and animations, all with significantly-fewer-bytes-received than other image formats! http://flif.info

Microsoft Edge seems to be unable to recognize that Flash Player is already enabled in the settings after the new update of windows 10.

In English there are few mistakes in reading synthesized speech (TTS), but errors in other languages by all means will occur.
For that reason, for textbooks in Japanese language of elementary school lower grades, recording with real voice is necessary.
Currently it installs and plays playback software, but it is ideal if it can open directly by the browser and play it.
Please support EPUB3 MediaOverlays playback.

Most browsers support the ability to drag and drop images from the browser to a folder on your taskbar or on your desktop. This makes it easy to quickly save images from a webpage. The closest thing Edge is able to do now, is making a shortcut to the url of the image. Which of course doesn't help.

Edge supports the WebM VP9 encoding in MSE but only when accelerated, or if the end-user modifies about:flags. This means that sites using WebM VP9 but not H.264 cannot rely on playback in Edge, as most computers do not yet have hardware VP9.

For sites like Wikipedia that avoid H.264 due to licensing policy, this leads to less efficient workarounds or lack of media usage. We would love to deploy Edge-compatible VP9 if it were usable. An opt-in API for JS would be acceptable.

Bonjour,
Chrome, firefox et autres lisent le webm en streaming que faire pour que Edge le fassse ?

This feature gives developers the ability to access Near Field Communication (NFC) functionality of a device, such as reading and writing NFC tags as well as exchanging data between NFC capable devices.

Editor's draft
https://w3c.github.io/web-nfc/

This API allow you to access USB devices from the browser.

It is a W3C editor's draft: https://wicg.github.io/webusb.

A user is prompted for permissions to access the microphone *each* *time* they access a page that calls getUserMedia().

This is makes web apps that are used regularly essentially unusable, because the user permissions dialog pops up at every page load.

Both FF and Chrome support persistent user permissions.