alex313031 / chromium-xp

Builds of Chromium for Windows XP/2003

  Chromium XP  

Builds of Chromium for Windows XP, Server 2003, and Windows 2000 (see win 2K caveats Here)

• Based on M49.0.2623.112
• Compiler Optimized
• Includes Codecs

I will be attempting to fix some things, backport some stuff, and use compiler optimizations from Thorium, except no AVX (will be using SSE2 as the baseline).

---

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs.

Learn how to Get Around the Chromium Source Code Directory Structure .

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug upstream, please file it at https://crbug.com/new. If you found a bug in this fork, please file it Here.

chromium-xp's Issues

Use Chromium 86 instead of Chromium 49

subject

Is it possible to have it do that?

Add SSL implementation from Supermium 121

On Windows XP the Chrome browser typically uses ciphers from Windows schannel.dll implementation. Unfortunately those are not maintained by Microsoft anymore, and therefore the regular Chrome versions, including your Chromium XP v49 are not able to display specific websites which do use newer ciphers like the Elliptic curve ciphers ECDSA* and so on.

As a test the following website can be used:
https://html5test.opensuse.org
This is just one of many many examples.

It will fail to render the page with
ERR_SSL_VERSION_OR_CIPHER_MISMATCH
on Chromium-XP v49 on WinXPSP3.

but on Supermium 121 (Chromium-fork) (and all Firefox based browsers also) the site will load fine.
Firefox does always bring its own SSL implementations. But the Chromium-based Supermium 121 browser https://github.com/win32ss/supermium , which is open-source, also managed to overcome that bug by adding its own SSL implementation.

Request is to do the same for your Chromium XP.

Not calling home to google on about:blank, possible?

Thank you very much for creating that nice project! It is very valuable for users of Windows 2003, Windows XP, and also for the ReactOS project! I tried to boost the popularity of your project a bit by reactos/rapps-db#202

A request for the start:
Given that the user set up about:blank as default homepage.
If I do open the browser, I can see via netstat -abn that it seeks contact to some legitimate google servers.
What does the browser try to obtain from there? Can we turn that off? (the official Google Chromium sources M49.0.2623.112 does behave the very same!)

The point of this fork

What's the point of this fork? Chromium 49 is 7 years old and has very, very limited compatibility with the current web. Will rendering engine get updated? Otherwise there's no point to work on 7 years old browser code.

When will a release be made?

subject

Sse2

I still have an old Pentium 4 around, so having this browser support sse2 would totally make it more awesome. I'm remembering when they just started making dual core available. When they stop having two cpus on tyan motherboards. Sad day.

Certificate Errors showing up under Windows Server 2003

Do not warn when --no-sandbox is passed

We do often intentionally use the --no-sandbox command line parameter as a workaround for running Chromium on ReactOS.
The browser warns then in the infobar, that this is not a recommended configuration.

Can we disable this warning per default in a future version?
I know there might be another command line flag to suppress that info-bar altogether, but that is a rather radical step.
If I remember correctly that was --disable-infobars
We do know what we are doing and we are aware of the security implications of --no-sandbox.