From MDN: The OffscreenCanvas interface provides a canvas that can be rendered off screen. It is available in both the window and worker contexts.

From me: It would be great to prepare images and run WebGL without tying up the UI thread.

https://developer.mozilla.org/en-US/docs/Web/API/OffscreenCanvas
https://www.chromestatus.com/feature/5424182347169792
https://wiki.whatwg.org/wiki/OffscreenCanvas

Support the ImageBitmap interface: https://developer.mozilla.org/en-US/docs/Web/API/ImageBitmap
This includes createImageBitmap() with the options object (with settings like premultiplyAlpha). This is useful for better performance for preparing images for use in a canvas. In particular it helps speed up WebGL texture uploads, since the decode & premultiply step can be done asynchronously in advance instead of inside the texImage2D() call.

It will also unblock other APIs like the "imagebitmap" rendering context and OffscreenCanvas.

Give users the ability to use custom themes to truly personalize their Microsoft edge. I have been looking for a Clone Army 501st Legion Star Wars theme for the Longest Time.

Please make <radialGradient>s behave like Webkit browsers!

https://codepen.io/brybrant/pen/gxVday

Thanks!

HEIF/ISO Base Media File Format
https://en.wikipedia.org/wiki/High_Efficiency_Image_File_Format

Support for advanced Canvas TextMetrics returned from context.measureText(), e.g. fontBoundingBoxAscent and actualBoundingBoxDescent.

https://www.w3.org/TR/2012/CR-2dcontext-20121217/#textmetrics

WebGL: Support CopyTexImage2D for floating point texture sources or destinations.

Edge only supports msToBlob() currently. Please support standard toBlob().

http://www.w3.org/TR/html5/scripting-1.html#dom-canvas-toblob

A similar feature was already present in Google Chrome. When you access a site that is experiencing difficulties of access for multiple users an error message would be displayed informing you of the widespread problem affecting other users.
This feature would be interesting for developers and users that have to make sure that the problem is not related to the user, but the website.

When loading progressive jpegs as background images, nothing shows until the whole image has loaded. I thought the point of progressive jpegs was to show the low resolution scan first, then build up to higher resolution as the image loaded.

The SVG 2 paint-order property allows authors to control the order in which stroke, markers, and fill are painted for each shape, or for text. This can be used to create outlines that do not obscure fine details of shapes or text. It can also be used to create more subtle line markers that do not obscure the line itself.

The basic fill/stroke/markers options, as defined in the current draft of the specification, are already supported in Firefox, Chromium, and Webkit. They are therefore unlikely to change, although additional options may be added by future specifications.

http://www.w3.org/TR/SVG2/painting.html#PaintOrder

Support the BackgroundImage and BackgroundAlpha input values in SVG filters.

SVG 1.1:
http://www.w3.org/TR/SVG/filters.html#BackgroundImage

SVG 2:
https://drafts.fxtf.org/filters/#valdef-in-backgroundimage

Test:
https://rawgit.com/tanty/design-hodgepodge/master/svg/filter/feBlend-backgroundimage-tests.html

Currently, using this value is even messing the rendering of the whole page:
https://github.com/MicrosoftEdge/Status/issues/307

Support for multiline / new line / carrige return within the <title> element inside an svg shape when rendering tooltip.

Tooltip currently does render, however is only all on one line.

https://jsfiddle.net/tt66gh9c/

<svg height="140" width="500">
<ellipse cx="200" cy="80" rx="100" ry="50" >
<title>this
is multi
line</title>
</ellipse>
</svg>

Thanks.

It would be fantastic if you could support the canvas context isPointInStroke method as per Chrome, Firefox, Safari.

It is by far the easiest way to do hollow-object arbitrary path-based hit testing (way easier than the unbelievably challenging, bounding-box-based hit testing proposed in the standard).

At the moment, we have some rather poor fallback code for IE/Edge that approximates it using a bit of iteration over isPointInPath().

Transferable CanvasProxy has been fully-specced for a while now. Along with constructable CanvasRenderingContext2D and WebGLRenderingContext, it allows rendering to a canvas element safely from another thread.

This would be an amazing performance advantage for graphics. Take the plunge!

https://html.spec.whatwg.org/multipage/scripting.html#canvasproxy

APNG is an extension of the Portable Network Graphics (PNG) format, adding support for animated images. It is intended to be a replacement for simple animated images that have traditionally used the GIF format, while adding support for 24-bit images and 8-bit transparency. APNG is backwards-compatible with PNG; any PNG decoder should be able to ignore the APNG-specific chunks and display a single image.

GIF vs. APNG vs. animated WebP: http://littlesvr.ca/apng/gif_apng_webp.html
Support status: http://caniuse.com/#feat=apng (Firefox and Safari 8 support APNG)
Specification: https://developer.mozilla.org/en-US/docs/Animated_PNG_graphics