Tag Archive: internet explorer


MIDAS and Internet Explorer 11

Here are MIDAS HQ we love getting feedback from our customers! Whether positive or critical, all feedback is important to us as it helps us to continually develop and improve our MIDAS room booking & resource scheduling software and service to make it the best it can be!

Our customer feedback is overwhelmingly positive, and you can read some of these comments on our website and also on independent review sites such as TrustPilot.

However, in recent times a handful of customers have commented specifically in relation to the user interface (UI) of MIDAS, which a few perceive as now a little “dated”.

We wanted to begin addressing this for our next MIDAS update, v4.20, and so we’ve introduced a number of changes and improvements in this area which you can read about in the following blog post.

However, we also thought it would be useful to explain some of the challenges we’ve faced with regards to the UI over the years.

As you may or may not know, MIDAS has been in continuous active development for well over a decade, and our philosophy has always been to support ALL popular web browsers (Internet Explorer, Mozilla Firefox, Google Chrome, Opera, Apple Safari, and more recently Microsoft Edge).

Room Booking System for Chrome, Firefox, Safari, Opera, and Edge This has been an enormous task over the years, but we feel strongly that our users should have a choice of which web browser they use, with a consistent MIDAS experience between browsers, and not be forced to use one particular browser in order to be able to access and use our MIDAS software.

It’s fair to say that the most difficult web browser to maintain support for over the years continues to be Microsoft’s Internet Explorer series, primarily because it has always lagged way behind all other vendor’s browser offerings in terms of its development, updates, and support for the latest standards (the web has developed and evolved significantly over the years we’ve been developing MIDAS, and Internet Explorer doesn’t keep up!).

To some extent we’ve been “held back” over the years by our decision to continue to support customers who force their uses to use Internet Explorer, however, as of today the only version of Internet Explorer we officially support is 11, having deprecated support for IE10 & 9, IE8, IE7, and IE6 over the past decade.

MIDAS and Internet Explorer 11 Continuing to support MIDAS in IE11 for the very small (and ever decreasing) percentage of our users who continue to use this old browser limits how we can develop MIDAS, particularly in terms of the user interface.

Whilst we would have loved to have dropped IE11 support long ago, Microsoft have committed to providing mainstream support for IE11 until the end of life of the operating systems upon which it is installed – namely, Windows 7, 8 and 10. Windows 7 & 8 have both now reached their EOL (End Of Life) for mainstream support, however Windows 10 is still actively supported by Microsoft and will continue to be for the foreseeable future (for a minimum of at least two years).

That’s why we’ve taken the difficult – but necessary – decision that at some point during 2019 we’ll officially be dropping IE11 support in MIDAS.

This won’t necessarily mean that MIDAS will suddenly cease to function for IE11 users next year, but it does mean that over time new features and new user interface elements and enhancements may not display or even function correctly if you continue to access MIDAS using Internet Explorer 11.

If you’re currently an IE11 user, there is however, plenty of time to switch to a different web browser and there’s plenty of choice when it comes to modern alternative web browsers.

MIDAS will continue to be supported in recent versions of Firefox, Chrome, Safari, Edge, and Opera.

We appreciate that this may affect a very small number of users, but we hope this blog post gives some insight and understanding as to why we’re making this decision and also gives you plenty of time to switch to an alternative, more modern, web browser.

As ever, if you have any questions or concerns over how this may impact you and your organization’s use of MIDAS, please don’t hesitate to contact us and our friendly team will be only too happy to help!

Microsoft Internet Explorer 12You may have seen articles recently on other websites and blogs claiming that as from today, 12th January 2016, Microsoft will end support for all versions of Internet Explorer, except for IE 11.

This isn’t strictly true!

What in fact Microsoft have announced is that “Beginning January 12, 2016, only the most current version of Internet Explorer available for a supported operating system will receive technical support and security updates“.

What this essentially means is that if you’re a Windows 7 user with Internet Explorer 9 or 10 installed, only Internet Explorer 11 will continue to be supported going forward.

However, if you’re a Windows Vista user, where the highest version of Internet Explorer that can physically be installed on that operating system is IE 9, then if you’re currently running IE 7 or 8, only IE 9 will be supported on your operating system going forward, so you should update to IE 9.

The following table from Microsoft outlines which versions of Internet Explorer they will continue to support as from today:

Windows Desktop Operating Systems Supported Internet Explorer Version
Windows Vista SP2 Internet Explorer 9
Windows 7 SP1 Internet Explorer 11
Windows 8.1 Update Internet Explorer 11
Windows Server Operating Systems Supported Internet Explorer Version
Windows Server 2008 SP2 Internet Explorer 9
Windows Server 2008 R2 SP1 Internet Explorer 11
Windows Server 2012 Internet Explorer 10
Windows Server 2012 R2 Internet Explorer 11

Our web-based room booking and resource scheduling software, MIDAS, is currently supported in IE9+ and all other major browsers.

Over the years we have previously dropped support for MIDAS in IE6 in 2011, IE7 in 2012, and most recently IE8 in 2013.

Whilst we have no immediate plans to drop support for IE9, it’s likely that our support for this aging browser will within the next couple of years. Therefore, if your using an older Windows operating system, like using Internet Explorer, and can’t update to a more recent version of Windows, then we’d encourage you to at least ensure that your browser is the most up-to-date it can be for your particular operating system.

You might also be interested in:
Windows 10 and Microsoft Edge now available
Could Internet Explorer go Open Source?

Microsoft Internet Explorer 12
Today the Internet Explorer Developer Relations Team at Microsoft have hinted on Twitter at the possibility that the browser may one day become “Open Source”.

“Open Source” is a term referring to software that whose source code is available for modification or enhancement by anyone. All other major web browsers (Mozilla Firefox, Google Chrome, Opera and Safari are based on open-source components). Presently, Internet Explorer is the only one of the big 5 browsers to remain entirely “closed source”.

As part of their #AskIE event on Twitter today, questions were invited on the current status and development of Internet Explorer. One question in particular was posed as to whether Internet Explorer would “ever consider going opensource to speed up develop/bug fixing?“, to which the response from the people behind the browser was “We consider many things!

Why is this significant?

Well, Microsoft have come under much criticism in the past over how slowly they release major updates to their browser. Five years passed, for example, between the releases of IE6 and IE7, and then another 3 before IE8! (Compare that with say Mozilla, who’ve been releasing major updates to Firefox every six weeks for some time now!). Whilst there were of course critical “security updates” and patches to IE in those big gaps between major releases, no “new features” or support for new web standards were introduced – meaning a headache for developers of websites and web based apps.

Developers had to ensure “backwards compatibility” with “stagnant” versions of IE, whilst at the same time wishing they could take advantage of newer web standards and technologies which all the other major browsers supported, but IE didn’t.

In the development of our popular browser based room booking system, MIDAS, we’ve had to take difficult decisions in the past to drop support for IE6, IE7 and then most recently IE8 – despite those browsers still having notable market share at the time we took those decisions.

To add to that, when Microsoft have released a “major” update to Internet Explorer, it’s not always available for all Windows Operating Systems. Windows XP users for example can’t run anything higher than IE8 (and if you’re still using Windows XP… well, you really shouldn’t be!!)

So how would Internet Explorer potentially becoming “open source” help?

Well, first of all, more developers would be able to get involved in the project by adding support for new and emerging technologies and standards. Secondly, it would also mean that bugs could be more readily identified and fixed. These two factors alone would undoubtedly lead to a faster release cycle, and greater compatibility with the latest standards!

To illustrate just how far behind other browsers Internet Explorer currently is (in terms of support for the latest web standards), IE11 (the current version of IE generally available) is only 67% – compared to Opera 22 and Firefox 30 on 85%, and Google Chrome 35 edging ahead with 86% compatibility with the latest web standards (Source: caniuse.com)

We’d love to see a faster release cycle for Internet Explorer and the same support for technologies and standards in IE that other browsers have had for some time!

Internet Explorer Developer Channel
On a positive note, earlier this week, a new “developer preview” of Internet Explorer emerged through the new “Internet Explorer Developer Channel“, to give developers like us a sneak peek at what to expect in IE12… the big question now is how long will it be until IE12 actually becomes available to end users? Will Microsoft wait until Windows 9 is released (Like they did with IE10 and Windows 8), or will we see the next major update to Internet Explorer sooner?

Let’s hope so!

You might also be interested in:
Mozilla: The browser vendor who USED to believe in equality and freedom of speech!
The Best Web Browser? Internet Explorer 11, Chrome 31, Firefox 25, Opera 17, or Safari 5?

Browser Logos

We put the latest web browsers head-to-head to try to find out which one is best!

In developing a powerful and feature-rich browser based room booking and resource scheduling system that’s supported in all five major browsers, we often get asked “So, which is the best web browser?”.

This time last year we put Chrome 23, Firefox 16, Internet Explorer 9 & 10, Opera 12 and Safari 5 head-to-head

Now, twelve months on, and less than a week since Internet Explorer 11 became available for Windows 7, Firefox celebrated its ninth birthday, and just a day after Google Chrome 31 is released, we decided it was high time to once again put the latest web browsers offerings “head-to-head” and independently, rigorously test and benchmark them to find out which one of the five major browsers is currently “the best”….

Browsers Tested

Google Chrome 31 Mozilla Firefox 25 Microsoft Internet Explorer 11 Opera 17 Apple Safari 5
Google Chrome 31 Mozilla Firefox 25 Internet Explorer 11 Opera 17 Apple Safari 5

The Tests

We broadly tested four key areas of browser performance: Speed, Memory Usage, Compliance with standards, and Javascript Performance.

1. Speed

Browser Benchmark: Cold Start The “Cold Start” test measures the time taken to load up the browser upon its first run after a computer reboot. This is measured from the point at which the browser is executed until the point at which its user interface (UI) is ready to accept input.

Browser Benchmark: Non-Cold Start The “Non-Cold Start” test measures the time taken to load up the browser on second and subsequent runs after its first run after a reboot. This is measured from the point at which the browser is executed until the point at which the user interface (UI) is ready to accept input.

Browser Benchmark: Initial Page Load Times With the browser open, an empty cache, and showing a blank page (about:blank), the “Page Load Time (No-Cached Load)” test measures the time taken to completely load a complex webpage. This is measured from the point at which the “Enter” key is pressed on the URL in the browser’s address bar until the point at which the test webpage has fully loaded (as reported by an “onLoad” event on the test webpage).

Browser Benchmark: Page Cache Load Times With the browser open, and the test webpage already loaded in a single tab, the “Page Load Time (Reload from Cache)” test measures the time taken to reload a complex webpage. This is measured from the point at which the F5 key (refresh) is pressed until the point at which the test webpage has fully reloaded (as reported by an “onLoad” event on the test webpage).

2. Memory Usage

Browser Benchmark: Base Memory Usage The “Base Memory Usage (Blank Tab)” test measures the amount of memory used by the browser with just a single blank (about:blank) tab open.

Browser Benchmark: Memory Usage with 10 open tabs The “Memory Usage (10 open tabs)” test measures the amount of memory used by the browser with 10 tabs open, each displaying the home page of a popular website.

3. Compliance

Browser Benchmark: HTML5 Standards Compliance The “HTML5 Compliance” test measures how well each browser conforms to the current state of the HTML5 specification.

Browser Benchmark: CSS3 Standards Compliance The “CSS3 Compliance” test measures how well each browser conforms to the current state of the CSS3 specification.

4. Javascript Performance

There are a number of different Javascript Performance Benchmark tests available today, all of which give quite different results. We’ve analyzed results from 6 of the most popular Benchmarking Tests and aggregated the results below:
Browser Benchmark: Javascript Performance Individual details of each of the 6 individual Javascript benchmark test suits used to arrived at these aggregated scores may be found in our full test report, available to view/download at the end of this page.

Summary

Category Test Winner Runner Up
Speed Cold Start FF25 IE11
Non-Cold Start IE11 SF5.1
Page Load Time (Non-Cached Load) OP17 IE11
Page Load Time (Reload from Cache) GC31 OP17
Memory Usage Base Memory IE11 SF5.1
10 Open Tabs FF25 SF5.1
Compliance HTML5 GC31 OP17
CSS3 OP17 GC31
Performance Javascript Performance (Aggregate) GC31 OP17

Results

1st Place 2nd Place 3rd Place 4th Place 5th Place
Google Chrome 31 Opera 17 Microsoft Internet Explorer 11 Mozilla Firefox 25 Apple Safari 5
Google Chrome 31 Opera 17 Internet Explorer 11 Mozilla Firefox 25 Apple Safari 5

The above overall positions were derived based upon the sum of the positions that each browser finished in in each of our tests. For example, in our HTML 5 compliance test, Chrome came first and so was assigned 1 point, Safari came 5th and so was assigned 5 points. Browsers were then ranked according to the lowest number of points to give the 1st-5th places above (1st being the best)

Analysis

Google Chrome 31 Google Chrome
When we last tested the five major browsers back in November 2012, Chrome came first in 8 out of 13 our tests, making it a clear winner!
A year later, and Chrome is still going strong, coming top in 8 out of 15 tests, and second in a further two tests.
Where Chrome still doesn’t perform quite as well is when it comes to its memory usage, using well over 3 times as much memory with a single blank tab open than Internet Explorer 11.

Mozilla Firefox 25 Mozilla Firefox
We were a little surprised that Firefox only came top in 3 out of 15 tests, and only once came runner up. To Firefox’s credit, its main strength still seems to be in its memory usage. With 10 websites open in separate tabs, the amount of memory used was less than half that of Chrome with the same ten sites open.

Microsoft Internet Explorer 11 Internet Explorer
We were pleasantly surprised by the improvement of Internet Explorer 11 over previous versions as well as other browsers.
IE11 came top in a couple of our tests, and runner up in a further three.
Where IE11 appears to have improved most over earlier versions of Microsoft’s browser in is the length of time taken to load and pages (either from a server, or from the cache) as well as start/restart the browser itself. In our tests, starting IE11 took just 0.01463 seconds! – some 280x quicker than Opera started.
That said, in general Internet Explorer 11 still has a way to go to come up to par with the other major browsers in terms of HTML 5 compliance.

Opera 17 Opera
A lot has changed with Opera since we last tested browsers twelve months ago. Since then, Opera have switched from using their own “Presto” layout rendering engine to instead using the same engine as Chrome.
Whilst this change has been received with mixed reviews by Opera users, with some unhappy that many of Opera’s original features were dropped, our test results actually show that the “new” Opera is a browser to be reckoned with, out performing Internet Explorer 11, Firefox 25 and Safari 5 in our tests.
Opera 17 came top in 3 out of our 15 tests, and runner up in 6.
The browser also scored highly on HTML5/CSS3 compliance and in our aggregated Javascript performance tests, however, Opera’s memory usage was fairly high, second only to Chrome. Opera 17 was slow to start, however, once running it loaded and rendered web pages swiftly.

Apple Safari 5.1 Safari
Our browsers tests were performed on a Windows machine (test specifics are included at the end of this report). Whilst the latest version of Safari is 7, Apple took the decision after the release of Safari 5.1 to no longer continue developing Safari for Windows users – a mistake in our view! Therefore, the most recent version of Safari available to Windows users is 5.1.7, which was used in our testing.
Given that Safari 5.1.7 is now the oldest of the 5 browsers tested, it follows that is doesn’t perform as well as its peers.
However, surprisingly, it did come runner up in both our memory tests as well as our non-cold start test.

Conclusions – From a Developers Perspective

From our perspective, as developers of a leading web-based room booking and resource scheduling solution, perhaps the most important factors in determining which browser is “best” are compliance with the latest HTML5 and CSS3 standards. As we work hard to ensure our software works well in all the major browsers, this is where having universal standards between browsers becomes so important. In theory, a website (or in our case, a web app), should look and behave the same regardless of the browser being used, which should in theory happen if all browsers complied 100% with standards! Chrome 31 currently comes the closest to the HTML 5 standard with 93% compliance, but as can be seen, CSS3 compliance still has a long way to go for all browsers, with the winning browser in the CSS3 compliance test (Opera 17) only achieving 58% compliance.

Speed (page load time) and Javascript Performance are also important factors for us, as we want our web app to be as fast and responsive as possible. Opera 17 and Chrome 25 loaded pages faster in our tests, with Internet Explorer 11 following close behind. As for performance, both Chrome 25 and Opera 17 outperformed other browsers in our aggregated Javascript performance test scores.

A few surprising finds:

  • Microsoft have made some significant steps forward with Internet Explorer 11 over earlier incarnations of their browser.
  • Opera 17 performed better than expected
  • Firefox 25 performed worse than expected, finishing an overall 4th place in our tests.
Online Web Based Room Scheduling MIDAS, our popular Browser-Based Room & Resource Scheduling Software is currently supported in all browser versions we’ve tested here. Find out more at https://mid.as

Conclusions – So which browser should I use then!?

• If you work with lots of browser tabs open at once, and/or the amount of available memory on your system is limited, Firefox 25 would seem a good choice of browser to use, as this used the less memory than other browsers under the same conditions.

• If you regularly open and close your browser, Internet Explorer 11 or Firefox 25 would seem a good choice as these browsers start up quickly. If, however, you tend to keep your browser running most of the time, Opera 17 would be a better choice, as even though its start-up time is considerably longer, initial page load times are the quickest of all the browsers we tested

• If you’re still using an earlier version of Internet Explorer – it’s certainly worth upgrading to IE11, or if that’s not possible (for example, if you’re using Windows XP, you won’t be able to update your Internet Explorer past version 8!), maybe it’s time to try a different browser!?

• At the end of the day, use the browser that you feel most comfortable with! …BUT make sure you keep it up-to-date, and don’t ignore the competition – if you do, you risk being left behind as other browsers overtake yours in terms of their speed, security, memory usage, standard compliance, and performance!

• In recent years, browsers such as Internet Explorer and Opera have been somewhat overlooked by many regular internet users – but if you’ve not used these browsers for years having previously dismissed them – a lot has changed, and it’s certainly worth giving them a second look again now!

View/Download The Complete Web Browser Test Report HERE

Test Specifics

Browsers Tested: Chrome 31.0.1650.48 m | Firefox 25.0 | Internet Explorer 11.0.9600.16428 | Opera 17 (Build 1652) | Safari 5.1.7 (7534.57.2)

Browser tests were performed on an Intel® Atom™ CPU D525 @ 1.80GHz system, with 4GB Ram, running Windows Home Server 2011 SP1 (Windows Server 2008 R2) 64-bit. Each browser was a clean install, using default install and browsers settings, and with no extensions/addons installed or enabled.

Speed tests were measured using Rob Keir’s millisecond timer and PassMark AppTimer v1.0. Each speed test was performed 10 times for each browser, and the results averaged to provide the data presented in this report.

Compliance Tests: HTML5 | CSS3

Javascript Performance Tests: Dromaeo | Speed-Battle | Sunspider | Peacekeeper | Octane | BrowserMark

Memory usage was measured 60 seconds after tabs had finished loading and was measured through the Windows Task Manager. Memory usage includes all associated processes running with the browser (for example, running Safari spawns both “Safari.exe” and “WebKit2WebProcess.exe” processes, the memory usage of both is taken into account)

The 10 sites open in tabs when measuring memory usage (10 open tabs) were:
//mid.as | http://news.bbc.co.uk | http://facebook.com | https://twitter.com | http://google.co.uk | https://youtube.com | http://wikipedia.org | http://linkedin.com | http://bing.com | http://amazon.co.uk

Test Date: 13 November 2013

Web Browser Roundup – April 2013

It’s been a busy few weeks in the world of web browsers… and there’s been some major changes in the browser landscape too! So here’s our take on what’s been happening..

  • Internet Explorer – IE11 coming later this year? / IE10 available for Windows 7 / Farewell IE8
  • Firefox – v20 now available… and a new rendering engine on the horizon?
  • Chrome – v26 out now… and ANOTHER new rendering engine on the horizon?!
  • Opera – 12.15 now available… and a change in rendering engine to.. WebKit? no wait.. Blink?
  • Safari – What will all these rendering engine changes to other browsers mean for Safari?


Internet Explorer:
Internet Explorer 11 coming soon
Microsoft are busy working on their next update for Windows 8, currently billed as being “Windows 8.1”, and expected to be available in the latter half of this year. Windows 8.1 will almost be a kind of “service pack” for Windows 8, but will also contain a number of improvements and updates to apps & software. Perhaps the most exciting updating coming with Windows 8.1 will be Internet Explorer 11. Yes, that’s right, no sooner is IE10 out of the door, but Microsoft are following it up with IE11 in a relatively short space of time (well, for them anyway!). We think this is great to see from Microsoft, as in the past updates to their flagship browser have been few and far between. Compare that with Mozilla’s current release cycle for Firefox, who are churning out a new version of Firefox every 6 weeks!

MIDAS will be supported in IE11 when it becomes available, however, it is unknown whether IE11 itself will be “exclusive” to Windows 8.1, or whether, like IE10, it will also be made available for Windows 7 users as well.

…and yes, you did read that right – Internet Explorer 10 is available for Windows 7 right now! (and has been for over a month). If you’re a Windows 7 and Internet Explorer user, we strongly recommend that you update to IE10 get the best out of MIDAS.

Finally, if you’re still an Internet Explorer 8 user please read our “Saying farewell to Internet Explorer 8” post and upgrade your browser… as we won’t be supporting MIDAS in IE8 indefinitely!

MIDAS is currently supported in Internet Explorer 8+ (v10+ recommended)


Mozilla Firefox:
Firefox 20
Mozilla’s rapid release cycle means that we’re now up to Firefox version 20! In a tweet yesterday, the Firefox team claim that with their latest version of Firefox “you can get the web up to 7 times faster than older versions”.

Mozilla also announced last week that they were collaborating with Samsung on a new rendering engine, named “Servo”. A “rendering engine” is essentially what converts raw web page code into what you actually see on your browser screen. Mozilla’s long standing rendering engine has been “Gecko”, but according to Mozilla, “Servo is a research project to develop a new web browser engine. Our goal is to create an architecture that takes advantage of parallelism at many levels, both on the CPU and GPU, while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. With Servo, we aim to take the kinds of fluid, richer multimedia experiences expected in today’s smart phone and tablet applications to the next level on tomorrow’s web and tomorrow’s hardware.”
“Servo” is still in its early days and according to Mozilla, “It’s too early to say how [Servo] will be adopted going forward. No decision has been made as to whether Servo will replace Gecko. Gecko remains the ‘productised’ web engine for Mozilla.”
So it may be that Servo ends up being a rendering engine for Mozilla’s smart phone/tablet browsers, and Gecko remains for desktop Firefox editions (which could get confusing!), or more likely in time, Mozilla will standardize their rendering engine across all platforms.

MIDAS is currently supported in Firefox 4+ (v20+ recommended)


Google Chrome:
Chrome 26
The current version of Google’s Chrome browser is v26. Ever since its first release – which was only 4 years ago! – Chrome has always used the WebKit rendering engine, which until then had most notably been used in Apple’s Safari web browser. Chrome’s subsequent input into the WebKit project has really driven WebKit development forward in the last four years, to the point that WebKit is arguably the most standards-compliant of all the rendering engines currently used by the major browsers.
However, Google recently announced that they would be developing a new rendering engine for Chrome, called “Blink”, which is expected to make it into builds of Chrome within just 10 weeks! Unlike Mozilla’s “Servo” engine, which is being built from the ground up, Blink is heavily based on the WebKit project.
Google have released a Blink Q&A video if you’re interested in learning more about this new rendering engine and its implementation

MIDAS is currently supported in Chrome 9+ (v26+ recommended)


Opera:
Opera 12.15
Opera are having a bit of a turbulent time of late, and in some respects appear to be loosing a sense of focus and direction!
Opera was first released in late 1994, making it the longest running browser that’s still in active development and current use today.
Apart from its longevity, what also makes Opera unique is their own “Presto” rendering engine.
Now, you may remember that back in January, we reported that Opera were making a switch from Presto to WebKit at least for their mobile browser offerings. Then in February, it was confirmed that Opera would drop Presto for their entire range on browsers (not just mobile).
This was a move that surprised a lot of analysts, and received a mixed response from Opera’s loyal user base.
Whilst it would have been sad to see a very mature rendering engine being put out to pasture, it would have meant that with Google and Opera both contributing to WebKit (along with Safari), it would not only provide more continuity between browsing experiences on the three browsers, but also with three major organizations contributing to the development of WebKit, it would have become very powerful and certainly have Mozilla and Internet Explorer (who don’t use WebKit) quaking in their boots!
…but this was before Google announced Blink… and shortly afterwards, Opera changed their minds and decided to also jump on the Blink band-wagon, after having gone all out and confirming they were moving to WebKit!!
So it’s a little confusing at the moment as to the direction that Opera are going to be going down! ..but as things stand at the moment, here are the list of rendering engines that the five major browsers are using/will be using in the near future:

Browser Current Rending Engine Future Rendering Engine
Trident Rendering Engine Internet Explorer Trident Trident
Gecko Rendering Engine Mozilla Firefox Gecko Servo?
Blink Rendering Engine Google Chrome WebKit Blink
Presto Rendering Engine Opera Presto Blink?
WebKit Rendering Engine Apple Safari WebKit WebKit

MIDAS is currently supported in Opera 9+ (v12+ recommended)


Safari:
Safari - The Future of WebKit
As you’ll know from our previous Web Browser Roundups – it’s been pretty quiet on the Safari development front in recent months, with not much happening!
Safari’s rendering engine is WebKit, and last month it looked like both Google and Opera would begin contributing code to the WebKit project (in fact, Opera even began contributing code to WebKit). This was before Google announced it was moving away from WebKit in favor of a new rendering engine, Blink, and then Opera followed suit and announced it was also teaming up with Google for the new Blink rendering engine.
So what will this mean for WebKit and the browser that will soon be the sole user and primary contributor to the WebKit project, Safari? Well, it remains to be seen! WebKit was successfully developed without Google’s input in the days before Chrome, so it may well survive without Google’s input in the future, but with Google and Opera pooling resources into Blink, and Firefox potentially introducing a new rendering engine too, the WebKit team (and Safari) are going to be facing a tough challenge to keep up!

MIDAS is currently supported in Safari 4+ (v5+ recommended)