microsoftedge/demos

Web pages and apps used to demo various DevTools, PWA, WebView, Extensions, and Web Platform features of Microsoft Edge

demos's Issues

The Todo demo's Readme needs a link to rendered demo page at github.io

The Readme
https://github.com/MicrosoftEdge/Demos/blob/main/demo-to-do/README.md
for the Todo demo needs a github.io link to the rendered demo page.
https://microsoftedge.github.io/Demos/demo-to-do/

Consider all demos' Readmes regarding such a link.

Do we need the devtools-quick-tips demo?

This repository has a devtools-quick-tips folder: https://github.com/MicrosoftEdge/Demos/tree/main/devtools-quick-tips

This isn't really a demo like the other ones, it doesn't have source code and can't be run. Instead, it's a collection of tips for how to better use DevTools.

For this reason, I'd prefer to remove it from this repository.

To avoid losing the information, I see a couple of possible options:

• Turn these tips into docs (on docs.microsoft.com), if they're not there yet.
• Rely on devtoolstips.org instead, which categorizes tips per browser: https://devtoolstips.org/browser/edge/ (you can also check a box to see only the tips that a particular browser only supports).

What do you think @codepo8 ?

Network Tutorial "Get Data" failure

Clicking on the "Get Data" button triggers an error, displayed in the Dev Tools window as "url scheme 'file' not supported, as a result no network activity occurs for this.

wrong path

Please put the dir "new-img" in add-new-images.html

img.src = add-new-images**/new-img/**${size}/${name};

keyboard shortcuts

How do I reconcile the browser's keyboard shortcuts with the PWA app's shortcuts, since I press many of them just to trigger the browser's functionality

Can the shortcut keys of the PWA application and the browser not conflict? This is a question I am thinking about. Customizing the shortcut keys of the PWA application does not affect the shortcut keys of the browser being used.

https://github.com/MicrosoftEdge/Demos/blob/main/demo-to-do/README.md

Change getBoundingClientRect to getTitlebarAreaRect in the 1DIV demo

Now that https://chromium-review.googlesource.com/c/chromium/src/+/3319288/ has landed, the WCO method name getBoundingClientRect has changed to getTitlebarAreaRect (also boundingRect changed to titlebarAreaRect in ongeometrychange event).

So we need to fix the 1DIV demo.