In the leaked Windows 9 screenshots, we noticed that build 9834 still has the old Internet Explorer 11 in it. Recently, Neowin reported that Microsoft has all new design for Internet Explorer 12 and it looks a lot like Chrome and Firefox. The main change is that URL bar will now appear below the tab bar, currently URL bar and the tabs bar are on the same line in IE11. Another main improvement comes in the area of extensibility as Microsoft has added support for extensions in Internet Explorer 12.
Today, Mary Jo Foley reported some more tidbits about the upcoming IE12. First of all, IE12 is codenamed ‘Spartan’ and it was also spotted with the same name in leaked Windows 9 build. Check the app ‘zSpartan’ below video in the new Start Menu. Bing app linking and task completion team has also mentioned Spartan in their recent job listing.
“The emergence of online services has extended web as an information repository to where users can take actions and complete tasks end to end, such as buying movie tickets, reserving a restaurant table, borrowing books, and getting a taxi. This trend is accelerated by the mobile devices, equipped with the mobile web to keep user always online, multiple sensors to extend user inputs from texts to speech, images, location and connect online to offline, cloud computation to enable intelligent inferences and large scale data mining, and native apps to deliver compelling user experiences. With this, search engine’s role is to connect people with services, turn intentions into actions lightning fast, and eventually make your mobile devices as your personal task assistant.”
Regarding extensions model for IE, Mary pointed out to an interesting Microsoft Research project which deals with extensions for browsers,
“Xax is a browser plugin model that enables developers to leverage existing tools, libraries, and entire programs to deliver feature-rich applications on the web. Xax employs a novel combination of mechanisms that collectively provide security, OS-independence, performance, and support for legacy code. These mechanisms include memory-isolated native code execution behind a narrow syscall interface, an abstraction layer that provides a consistent binary interface across operating systems, system services via hooks to existing browser mechanisms, and lightweight modifications to existing tool chains and code bases.”
Read about it in detail from the link below.