With binary data becoming more and more common in the browser, thanks to ArrayBuffers and TypedArrays and all the specifications that use them, we need to be able to properly log these data types to the console.

On the surface this is possible with console.log(), but is that is severely lacking when it comes to binary data. So I would like to propose the ability to log binary data in the classic hex dump format. Having a console.hex() command in the browser would certainly my my life of lot easier and probably a lot of others that work with binary data too!

For details, see this issue at whatwg / console: https://github.com/whatwg/console/issues/121

EDGE has a nice feature where users can highlight text on a webpage, and then send a copy(?) of that webpage to other users, with the annotations on it. Edge also can do this now with PDFs. The next logical step, from my point of view as a developer, is to let webpage javascript get information from these highlights. For instance, lets suppose I use html 'frames tag' to host one webpage in another. My user highlights the page (or HTML) in that frame, and an event fires letting me capture the text that he highlighted. Conversely, if my code wants to highlight something for the user, it should be able to do that. There would be an advantage would be for PDFs, since I myself have coded (though not perfectly) highlighting for regular web content, and so has a company called 'genius.com'. PDFs often have math formulas or special formatting that cannot be shown properly in HTML.

Thanks.

I would love to see some tooling surrounding ReactJS development. While I believe that on your competitors (Chrome/Firefox) these were developed by the community (or the vendor themselves...FB). I would love to see a CTA by Microsoft for this to be developed possibly following the example of Taylor Otwell surrounding his CTA to have Vue.js testing abilities added to the library.

Granted if Microsoft were to build the tools that would be amazing, but I don't think (in the day and age where Microsoft is so open source) that Microsoft calling on the community for a specific task should be ruled out.

So please either build ReactJS tools yourself or issue a call to action for the community (or FB directly)!

The F12 tools should improve how the user-agent override is exposed in two ways.

For Custom, the edit control is too tiny. It should be a large, even multi-line control with wrap. The existing control is too small to see any reasonable user-agent.

For all other selections, F12 doesn't display the value used. My suggestion is to all use the same multi-line control suggested above but that the control is read-only when any value other than custom is selected. Make sure that it is read-only but not disabled so that users can select and copy the value that will be used.