Microsoft Edge: Building a safer browser
blogs.windows.com
Microsoft Edge: Building a safer browser
1–10 of 75 posts
Re: Microsoft Edge: Building a safer browser
#2Features built or under consideration [0]
Re: Microsoft Edge: Building a safer browser
#3> Microsoft Edge provides no support for VML, VB Script, Toolbars, BHOs, or ActiveX.
Years too late of course, but good to see this finally happening.
Re: Microsoft Edge: Building a safer browser
#4> Microsoft Edge provides no support for VML, VB Script, Toolbars, BHOs, or ActiveX. Years too late of course, but good to see this finally happening.
This is definitely a case of "better late than never", IMO.
Microsoft browsers will always have a foothold in enterprise environments, and the prospect of developing against a "real" browser when working with enterprise customers is rather exciting.
Re: Microsoft Edge: Building a safer browser
#5Having met the engineers who actually built Edge, I can say with some confidence that I think this will the Microsoft browser people actually like.
They built it from the ground up with security in mind, and with standards compatibility at the expense of backwards compatibility.
In other words, they have finally decided that it is ok to tell their lagging enterprise customers to get with the times.
Re: Microsoft Edge: Building a safer browser
#6Microsoft has one helluva hole to dig themselves out of, here.
Re: Microsoft Edge: Building a safer browser
#7I believe that Microsoft not releasing versions for Linux / Mac OS X is going to not allow Edge to get maximum adoption.
How am I supposed to test that my website works on Edge properly? The only option thus far is to setup a VM with Windows 10 on it so that I can run a browser to test my website.
I dont even bother testing stuff on IE x for that reason.
Re: Microsoft Edge: Building a safer browser
#8> MemGC (Memory Garbage Collector) is a memory garbage collection system that seeks to defend the browser from UAF (Use-after-free) vulnerabilities by taking responsibility for freeing memory away from the programmer and instead automating it, only freeing memory when the automation has detected that there are no more references left pointing to a given block of memory.
Interesting; I don't think this has been announced before. It sounds similar in concept to Chrome's Oilpan (still not shipped AFAIK).
Re: Microsoft Edge: Building a safer browser
#9> The largest change in Microsoft Edge security is that the new browser is a Universal Windows app. .... This provides the user and the platform with the confidence provided by other Windows store apps
I see it's going to be a Windows Store app.
I wonder how this will affect the usability for people like myself, who never see the metro side of windows unless I accidentally move the mouse near the wrong side of the screen, or accidentally hit the Windows key. Any time I see a metro app like the horrendous metro version of Windows Update, I moan that it's there like a false positive, close it and find the normal version that isn't awkward to use.
Re: Microsoft Edge: Building a safer browser
#10> The largest change in Microsoft Edge security is that the new browser is a Universal Windows app. .... This provides the user and the platform with the confidence provided by other Windows store apps I see it's going to be a Windows Store app. I wonder how this will affect the usability for people like myself, who never see the metro side of windows unless I accidentally move the mouse near the wrong side of the sc…
Widnows 10 does not have fullscreen apps like windows 8 did