347 votes17 comments · Universal Windows Platform » XAML/Controls APIs (UWP) · Flag idea as inappropriate… · Admin →
This will be possible in Windows 10 Creators Update.
Starts about 3:00 in. Once documentation is on dev center, i’ll close this out.
143 votes11 comments · Universal Windows Platform » XAML/Controls APIs (UWP) · Flag idea as inappropriate… · Admin →
299 votes25 comments · Universal Windows Platform » XAML/Controls APIs (UWP) · Flag idea as inappropriate… · Admin →
Currently being spec’ed out.
I think the original suggestion has been taken down because discussion was becoming non constructive.
I am not opposed to this suggestion but I don't think this is a priority at all and I would prefer to see the Edge team move fast rather than spending time on this one.
Here are the reasons I see :
- The is a huge community community
- The IntelliSense c# developer love will be there if you choose to use Typescript
- async await c# developers are addicted to are already in preview
- Typescript is very easy to learn for a C# developer
In addition I'm curious to hear about those companies who chose to invest massive money to build .net browser extension. I think C++ was more common.
Async/await are now supported by default in Windows 10 build 14316 and above.
That would be so great ! I must agree with Alexander.
SVG2 is now on the Microsoft Edge backlog. You can track status updates at https://dev.modern.ie/platform/status/svg2/
Support for using CSS Transforms on SVG elements is now on the Microsoft Edge backlog with a priority of medium.
CSS Motion Path is currently on the backlog with medium priority. The status can be tracked at dev.modern.ie/platform/status/cssmotionpath
I must disagree with RobertWG. Performance improvement would be great even if it only addresses Windows 10+ . Don't fall into the legacy **** again (like it was the case with IE).
1 voteCyprien Autexier shared this idea ·