Microsoft begs Web devs not to make WebKit the new IE6


Recommended Posts

IE across the board sucks and from IE6 to IE9 has broken the web over and over again.. and then Microsoft starts coming out and complaining how everyone is using webkit (an open source browser engine that is absolutely KICK ASS) and because they are adding new features (who btw, will most likely be adopted by WHATWG and W3C eventually).

Wtf are we talking about.. and yes.. IE 10 sucks compared to every other browser. Just because it's a bit more compliant with HTML5 as a standard still doesn't make it great.. it makes it suck less.

Amazing how using webkit only prefixes breaks the web too right?

According to your logic (again) IE6 had 90%+ of the browser marketshare so everyone should have just followed Microsoft's broken standards because you know they "eventually" would have made it in.

The Microsoft "sponsored" HTML5 test that you keep claiming is BS comes DIRECTLY from the W3C, you know the people who are responsible for maintaining the specification. What are you going to claim next Microsoft pays off the W3C?

You and others didn't refute anything but just whine and defend garbage that Microsoft is and was in regards to IE browsers. The reason web is still have trouble moving forward is Microsoft and IE and nobody else.

You should learn to read. Microsoft is asking people to move the web forward by NOT using browser prefixes.

The reason why IE6 was so terrible was because Microsoft used IE only prefixes and refused to follow set standards, by using webkit only prefixes you're just repeating the same mistakes MS made.

It's about time for you to shut up because yet again you just proved that according to you Microsoft can do no right and Google can do no wrong. It's sad because if this was a post about how Apple was pushing the web forward with HTML5 and dropping proprietary extensions you'll be all up in arms and start claiming that HTML5 is terrible and how flash is the savior of the internet. But since supporting HTML5 makes Google look good in this topic (according to you anyways), you're all for it.

Microsoft isn't asking people to use IE, they aren't asking people to not use Webkit. They're asking people to follow standards. Too bad you're too much of a fanboy to realize that.

You don't know what you're talking about which is why you have to rely on insults. You constantly undermine your own arguments with your nonsensical personal attacks and it's not worth discussing anything with you if you can't post sensible comments.

That's ridiculous. Ignoring the fact that webkit has a tiny share of the desktop market and the mobile market isn't big enough yet to matter, what you're advocating is no different to the situation that existed when IE6 owned the market. The only standards that matter are the ones agreed by W3C and other bodies and it's up to browsers to maintain compatibility.

I'll just let this assertion that the rendering engine of choice for the number 1 web browser for the desktop "has a tiny share" speak for itself :laugh:

Duh.. so they will use IE.. LOL..

I sugest you re-read what you quoted again, and this time ACTUALLY read it.

I'll just let this assertion that the rendering engine of choice for the number 1 web browser for the desktop "has a tiny share" speak for itself :laugh:

The number one what ? http://www.netmarketshare.com/browser-market-share.aspx?qprid=0&qpcustomd=0

  • Like 2
I sugest you re-read what you quoted again, and this time ACTUALLY read it.

It's gone from him trying to defend a "point" and completely ignoring what's right in front of him to "screw standards derp Webkit". You're wasting your time.

  • Like 2

Don't know where they get their stats from because every other site I look at puts Chrome ahead of them

http://www.w3schools.com/browsers/browsers_stats.asp

http://gs.statcounter.com/

Yeah, the only difference is that Webkit is open while IE was and still is proprietary. It's a night and day difference. Not to mention that browsers who use Webkit (Safari, Chrome) are updated transparently to the user making the very latest version immediately adopted at 90% marketshare.

It's not even beginning to compare to IE6 and never will.

IE10 will continue to linger just like everything microsoft and IE long after IE 11 is out and this fragmentation is the worst thing that has caused the web the biggest damage in progressing forward.

Like it or not, MS has the corporate world to think about where controlling versions is paramount to the IT staff. Having IE simply update transparently like Chrome or FF would be a massive no. All updates have to be approved and having WSUS manage windows updates is how things work. It maybe an idea to have a setting that can be managed via group policy (and is default on domain joined machines) which stops transparent updating and all other machines (home users etc.) do get the latest versions, but MS also has to deal with the EU and browser ballot (which is just mind numbingly annoying now - EU, we want a browser ballot choice, I don't want it).

Again, the standards organizations MADE a standard for touch controls that all browsers decided to follow. Google decided to make their own incompatible and non compliant and in fact a worse implementation. of touch controls and not implement the standard one.

you keep ignoring this little fact, the standard already existed, Google's method isn't going to be a standard, they already had a standard, a better standard.

And we're not defending MS, we're arguing to Google shouldn't make their own standards when there are already standards for it.

standards.png

Don't know where they get their stats from because every other site I look at puts Chrome ahead of them

http://www.w3schools...wsers_stats.asp

http://gs.statcounter.com/

And btw, that's not IE10.. that's IE all versions in existence combined.

One of the major problems why other browsers and Webkit especially are all better than IE is the speed of updates.

For example.. Chrome and Firefox and pretty much every major browsers today (minus IE) updates the browser automatically and transparently. This means that over 90% of the users will always have the latest version of the browser at any time. They don't have to worry about updates.. Chrome and Firefox, upgrade themselves transparently and next time you click that browser icon to start it you will be running the latest version.

This is HUGE for moving the web forward as all of these browsers innovate and add features much faster than Microsoft and that's one of the biggest reasons why IE will always break the web. Next year, every webkit and other browsers will support the very latest HTML5 spec as they are officially added and IE users will have to wait for Microsoft to release IE11 and in the meantime you will have a certain amount of people still using IE 10. This si why Microsoft was and will be toxic for moving the web forward.. aside from their tendency to completely tie IE and everything they do to their own business interests and platform.

Like it or not, MS has the corporate world to think about where controlling versions is paramount to the IT staff.

Who cares? I don't care if they have corporate world to think about.. They have ruined the web and because of their approach they are unable to quickly upgrade and innovate. Who's fault is that? This is why they are being steamrolled by everyone. Nobody is going to wait for them anymore.

Hopefully more and more enterprises switch to webkit powered browsers and dump IE once and for all, especially now when they are adopting iOS and Android tablets and other stuff across Fortune 500 companies.

And btw, that's not IE10.. that's IE all versions in existence combined.

One of the major problems why other browsers and Webkit especially are all better than IE is the speed of updates.

For example.. Chrome and Firefox and pretty much every major browsers today (minus IE) updates the browser automatically and transparently. This means that over 90% of the users will always have the latest version of the browser at any time. They don't have to worry about updates.. Chrome and Firefox, upgrade themselves transparently and next time you click that browser icon to start it you will be running the latest version.

This is HUGE for moving the web forward as all of these browsers innovate and add features much faster than Microsoft and that's one of the biggest reasons why IE will always break the web. Next year, every webkit and other browsers will support the very latest HTML5 spec as they are officially added and IE users will have to wait for Microsoft to release IE11 and in the meantime you will have a certain amount of people still using IE 10. This si why Microsoft was always toxic for the web.. aside from their tendency to completely tie IE and everything they do to their own business interests.

way to completely miss (or ignore) the post 2 above yours

Like it or not, MS has the corporate world to think about where controlling versions is paramount to the IT staff. Having IE simply update transparently like Chrome or FF would be a massive no. All updates have to be approved and having WSUS manage windows updates is how things work. It maybe an idea to have a setting that can be managed via group policy (and is default on domain joined machines) which stops transparent updating and all other machines (home users etc.) do get the latest versions, but MS also has to deal with the EU and browser ballot (which is just mind numbingly annoying now - EU, we want a browser ballot choice, I don't want it).

For example.. Chrome and Firefox and pretty much every major browsers today (minus IE) updates the browser automatically and transparently. This means that over 90% of the users will always have the latest version of the browser at any time. They don't have to worry about updates.. Chrome and Firefox, upgrade themselves transparently and next time you click that browser icon to start it you will be running the latest version.

Starting with IE10, IE updates the browser automatically:

ie10-about_thumb.png?w=373&h=298

You really need to stop being a hypocrite and recognize that proprietary extensions are bad for the web... they were bad when IE6 ruled, and they are bad today. And as proponents of webkit have argued before, competition drives innovation... so why advocate for the elimination of all competing rendering engines like you have?

And your assertion that webkit is the standard because it has the most marketshare is silly and majorly hypocritical. Standards bodies make standards, not the browser with the largest marketshare.

It's amazing how the tables have turned.

Hopefully more and more enterprises switch to webkit powered browsers and dump IE once and for all, especially now when they are adopting iOS and Android tablets and other stuff across Fortune 500 companies.

And the first thing those corporations will do (if they switch) is disable auto-update. If you think corporations are going to allow silent auto-updating you're insane.

So you're going to be stuck with the same problem, just with a different browser.

And MS does update the browser in between major versions, you just don't know about it unless you're looking at WU and the full version string. Granted its not as frequent as chrome but starting with 10 it will be.

And btw, that's not IE10.. that's IE all versions in existence combined.

One of the major problems why other browsers and Webkit especially are all better than IE is the speed of updates.

For example.. Chrome and Firefox and pretty much every major browsers today (minus IE) updates the browser automatically and transparently. This means that over 90% of the users will always have the latest version of the browser at any time. They don't have to worry about updates.. Chrome and Firefox, upgrade themselves transparently and next time you click that browser icon to start it you will be running the latest version.

This is HUGE for moving the web forward as all of these browsers innovate and add features much faster than Microsoft and that's one of the biggest reasons why IE will always break the web. Next year, every webkit and other browsers will support the very latest HTML5 spec as they are officially added and IE users will have to wait for Microsoft to release IE11 and in the meantime you will have a certain amount of people still using IE 10. This si why Microsoft was and will be toxic for moving the web forward.. aside from their tendency to completely tie IE and everything they do to their own business interests and platform.

Who cares? I don't care if they have corporate world to think about.. They have ruined the web and because of their approach they are unable to quickly upgrade and innovate. Who's fault is that? This is why they are being steamrolled by everyone. Nobody is going to wait for them anymore.

Hopefully more and more enterprises switch to webkit powered browsers and dump IE once and for all, especially now when they are adopting iOS and Android tablets and other stuff across Fortune 500 companies.

Ignored the important stuff again huh, and the fact you didn't read you last quote

Yeah, the only difference is that Webkit is open while IE was and still is proprietary. It's a night and day difference. Not to mention that browsers who use Webkit (Safari, Chrome) are updated transparently to the user making the very latest version immediately adopted at 90% marketshare.

It's not even beginning to compare to IE6 and never will.

IE10 will continue to linger just like everything microsoft and IE long after IE 11 is out and this fragmentation is the worst thing that has caused the web the biggest damage in progressing forward.

That which has market dominance is the de facto standard. Or that which is ratified by a Standards organization. Which is Webkit? It's open, open does not equal standard.

If you prefer it, fine. Just don't become another liar. It is either a standard, or it is not. Whether or not it's open source (which I generally find to be inferior and less secure, my personal opinion and experience) is irrelevant to whether or not it is a standard unless it has market dominance making it the de facto standard.

I think the fact there are idiots still defending this after being clearly told this is about standards and not Microsoft, clearly illustrates that Webkit is already far worse than IE6 ever was.

Time to start notifying Webkit users that their browsers are enemies of the open web.

  • Like 3

Riiight.. the ONLY proper test is the one sponsored by Microsoft that shows IE10 doing well with HTML5.. GOT IT!

Tests sponsored by Microsoft actually test something.

HTML5 tests that you cling to for your sanity (or endless trolling) are like political push polls.

Yet update process is drastically outdated. Still long and requires reboot...

Newsflash: Some updates still require you to reboot your Windows PC. Le Shock and Horror! An integral part of the Operating System required a reboot to update.

But there is IE10 RC itself, which shows installation procedure very well. It didn't change.

That's for updating from IE9 to IE10. IE9 doesn't have the built-in ability to automatically update. IE10 does.

We're talking about starting with IE10.

Tests sponsored by Microsoft actually test something.

HTML5 tests that you cling to for your sanity (or endless trolling) are like political push polls.

Sites objectively testing open source browsers are a "political push polls" (whatever that means) while in your eyes tests paid by a corporation trying to show their browser as good for their own benefits is A OK..

Logic escapes you.

Sites objectively testing open source browsers are a "political push polls" (whatever that means) while in your eyes tests paid by a corporation trying to show their browser as good for their own benefits is A OK..

Logic escapes you.

Still ignoring the earlier replies I see.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      186
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!