Reactos Install Internet Explorer

Download Latest Version ReactOS-0.4.13-iso.zip (126.9 MB) Get Updates. Get project updates, sponsored content from our select partners, and more.

I proudly announce that ReactOS Deutschland e.V. has hired Jérôme Gardou to work full-time on the ReactOS kernel’s memory manager for the next 3 months.Jérôme is a ReactOS veteran who has been contributing to the project since 2009. He has deep expertise into nearly all parts of ReactOS, ranging from various user-mode components (mostly related to low-level graphics) over their kernel-mode counterparts and down to bare-metal components like the kernel memory manager.

Some people might think that ReactOS doesn't come with a Web Browser.Actually,it does!(I knew that it does). The page ReactOS Explorer is a short article on something that should have a lot more information written on it. If you know anything else about it, you are STRONGLY encouraged to add the information in. If you are unsure of proper formatting or style, add it to the talk page or this page itself as you think best and others will help.

We are building a website for one of our clients, and he told me one day that, one of his potential client couldn’t see the site using Internet Explorer. Then we quickly realized that there are still people out there using old versions of Windows and didn’t have any other browsers than the old Internet Explorer. Brought back a lot of good memories when I first started at Amazon and had to work on IE 6 compatibility issues.

We used mainly React for the business logic, and Ant Design for styles and interactions, so first thing we looked at is the React documentation on JavaScript environment requirements. So we added the following to the entry point index.js of our create-react-app.

We restarted the app, and found that the script still didn’t load on IE. So we looked into the error in dev console:

After quick search on Google, we found that we needed to polyfill the string methods as well, so adding another polyfill for that:

We have used react-intl and we found an error message in IE. And there is a link describing the issue here on how to fix, so we followed and added those as well.

Then viola! the site is running again! But wait, the styling is off. I spent a whole day on IE 9 trying to figure out what was going on. What I noticed was that the CSS was loaded, but partially. The antd styles were there but the custom CSS we wrote wasn’t loading.

After some research and consulting with friends, I stumbled upon this 6 years old Stackoverflow post then I quickly realized that it was the CSS selector limit on IE 9 that was causing the problem.

There are a few solutions we can take, but for the sake of going through everything and make the site work first, I chose to load antd stylesheet separately via CDN. And the styles showed up. But of course they didn’t look right because CSS Flexbox is not supported in IE 9. Even IE 10 the syntax is different.

I proudly announce that ReactOS Deutschland e.V. has hired Jérôme Gardou to work full-time on the ReactOS kernel’s memory manager for the next 3 months.Jérôme is a ReactOS veteran who has been contributing to the project since 2009. He has deep expertise into nearly all parts of ReactOS, ranging from various user-mode components (mostly related to low-level graphics) over their kernel-mode counterparts and down to bare-metal components like the kernel memory manager.

Some people might think that ReactOS doesn't come with a Web Browser.Actually,it does!(I knew that it does). The page ReactOS Explorer is a short article on something that should have a lot more information written on it. If you know anything else about it, you are STRONGLY encouraged to add the information in. If you are unsure of proper formatting or style, add it to the talk page or this page itself as you think best and others will help.

We are building a website for one of our clients, and he told me one day that, one of his potential client couldn’t see the site using Internet Explorer. Then we quickly realized that there are still people out there using old versions of Windows and didn’t have any other browsers than the old Internet Explorer. Brought back a lot of good memories when I first started at Amazon and had to work on IE 6 compatibility issues.

We used mainly React for the business logic, and Ant Design for styles and interactions, so first thing we looked at is the React documentation on JavaScript environment requirements. So we added the following to the entry point index.js of our create-react-app.

We restarted the app, and found that the script still didn’t load on IE. So we looked into the error in dev console:

After quick search on Google, we found that we needed to polyfill the string methods as well, so adding another polyfill for that:

We have used react-intl and we found an error message in IE. And there is a link describing the issue here on how to fix, so we followed and added those as well.

Then viola! the site is running again! But wait, the styling is off. I spent a whole day on IE 9 trying to figure out what was going on. What I noticed was that the CSS was loaded, but partially. The antd styles were there but the custom CSS we wrote wasn’t loading.

After some research and consulting with friends, I stumbled upon this 6 years old Stackoverflow post then I quickly realized that it was the CSS selector limit on IE 9 that was causing the problem.

There are a few solutions we can take, but for the sake of going through everything and make the site work first, I chose to load antd stylesheet separately via CDN. And the styles showed up. But of course they didn’t look right because CSS Flexbox is not supported in IE 9. Even IE 10 the syntax is different.

There are a fewsolutions for fixing the Flexbox issues in IE, and eventually we are going to try these. However, before we tried to fix Flexbox issues, I was trying to type on the form but none of my keystrokes register. Ugh. This issue pretty much put the nail in the coffin for IE 9 compatibility for now with our solution. I suspect the rc-form component had something that made it not work in IE 9.

So for now what we are doing with our client, is that we support everything down to IE 11, and we made sure that they look right. For IE 10, we will make it work but not look right.