Microsoft begs Web devs not to make WebKit the new IE6


Recommended Posts

Redmond doesn't want Internet Explorer 10's standards compliance to go unnoticed.

Internet Explorer 10 is a fast browser with good standards compliance, and the version of Internet Explorer 10 included with Windows Phone 8 is no exception, as it's almost identical to its desktop sibling. But Internet Explorer 10 has a problem: Web developers don't expect to see it on the mobile Web. The mobile Web is dominated by WebKit-based browsers, and mobile sites tend to be developed exclusively for, and tested exclusively on, WebKit browsers. A similar problem exists for tablets.

Often the development is even narrower; although both Android and iOS sport WebKit-based browsers, iOS is the one that dominates mobile browser usage, and dominates testing as a result.

This situation is all rather familiar; WebKit, especially on iOS, is occupying a similar position to that once held by Internet Explorer 6 on the desktop, where Web content was "best viewed in Internet Explorer 6" and was prone to breaking in Netscape or Firefox.

Keen to avoid being left out, Microsoft is imploring Web developers to adapt their sites. In a recent blog post, the software giant explains a variety of ways in which devs can update their sites to work well in browsers other than WebKit. Key to this was proper handling of incompatible features.

There are several sources of incompatibility. The hardest case is features that are simply proprietary to WebKit; these need to be worked around in some way or other.

Most other cases are a result of the standardization process used for Web specifications. When a CSS or JavaScript specification is under development and still subject to change, browsers implementing it are supposed to add a browser-specific prefix to the pieces of CSS or JavaScript they use. So for example, while still in development, WebKit's implementation of CSS rounded borders should use properties like -webkit-border-radius. Once the standard is stable and a browser is implementing that stable standard, the property should be renamed to simply border-radius.

For some standards, both browsers implement the stable version, without any prefix required. However, developers often fail to update their pages to accommodate this improving standard conformance, leaving their pages using prefixed properties, but not including equivalent unprefixed code. In this case, the solution is typically to remove the prefixes. Sometimes, the spec still isn't stable and the different browsers implement mutually incompatible versions of the spec, each with their own prefixes. In this case, the properties must be translated from one dialect to the other.

There are also some cases where the translation is more complex still, particularly when it comes to handling touch input. Apple pioneered work in this field in Safari, and a specification called Touch Events based on Safari (but created without Apple's involvement) is currently a Candidate Recommendation from the World Wide Web Consortium (W3C), the body that works on producing Web standards. Microsoft has proposed an alternative system called Pointer Events which would handle not just touch but also mouse and pen input in a consistent way. For both technical and legal reasons, W3C has decided that rather than work on Touch Events version 2, all future development in this area will be to Pointer Events.

The problem for developers is that WebKit supports Touch Events; Internet Explorer 10 supports a prefixed version of Pointer Events. Translating between the two should be broadly possible, but there are nuances to this; it's not simply a case of doing a quick search and replace.

For those who remember the Internet Explorer of the late 1990s and early 2000s, Microsoft's stance may seem a little amusing ? the company wasn't so bullish on following standards back when it commanded more than 90 percent of the browser market share. Redmond has been banging the "use standards" drum for some years now, and has been actively participating in standard development and stabilization.

http://arstechnica.c...it-the-new-ie6/

IE needs to die completely.. end of..

and, no, IE8, IE9 and IE10 will be the new IE6. Apple and Google along with Mozilla are following W3C and WHATWG in implementing new features and support for CSS3 and HTML and thus when we build web stuff today it just works across all of these browsers with most of the fancy effects and we are still jumping hoops and having to put up with Microsoft's IE crap.

So ironic but expected that Microsoft can't understand why they are terrible in this regard as well. IE 10 is better than all other IEs but it's STILL IE and it's still Microsoft, so we will continue supporting webkit because it evolves and browsers update themselves to be always current on user's machines while Microsoft still peddles their old proprietary crap..

Hey Microsoft, here's an idea for you.. MAKE IE based on webkit and help build a better webkit base since it's open and help developers develop for one HTML/web engine? Oh you don't want to, or you have to deal with your users who you screwed with terrible IEs? Well the web and internet in general won't wait for you. Nobody cares what you think anymore. You have shown us what web looks like with you and it's not a pretty picture and it's so ironic that we are being warned by MS about competing rendering engine not being "good" for us.

Just die already and stop whining since you are a decade late to the next generation.

  • Like 2

If microsoft really cared about web developers and standards compliance they would release IE10 for vista and backport the necessary technologies for it to run. In april 2014 i'm sure we will see a lot of website drop support for IE6 but unfortunately vista came with IE7 if i remember correctly so they can't really ditch IE7 or IE8 for quite some time.

Good to see Boz supporting the use of proprietary extensions and opposed to standards compliance. I guess it's easier than having to defend Microsoft.

Webkit is the standard. For both desktop and mobile. End of.

And btw, if Microsoft wants what's best for developers it should, as I said, dump their IE engine completely, join Webkit movement and create IE based on webkit and then contribute to the webkit based along with Apple, Google to improve it, so we can have finally one HTML rendering engine standard. Mozilla, btw, should do the same.

They can still make their own JS engine (like Google does with V8 and Apple does with Nitro) if they want to to compete on speed or add unique features to their IE browsers (actual browser features not how it renders content) and we can finally build developer tools and all kinds of design support and fancy effects when we have all major browsers on a single, universal rendering engine.

This would truly move the web forward in ways unseen before. Actually it would give us a terrific web platform that would be similar to Flash (and I mean from the compatibility standpoint) and we could finally build stuff that's creative and pushing the envelope instead of polluting our code with 15 different hacks just to render content properly on IE browsers.

Given that Webkit is an open source rendering engine, The argument about proprietary bits is stupid. Either open the source to Trident, or examine Webkit and build better support for those features into IE. Sounds like Microsoft are pulling an Apple here and blaming someone else for their lazy coding.

IE needs to die completely.. end of..

What a load of rubbish.

IE10 is a superb browser and Firefox, Chrome et al need to take a few lessons from it.

Standard compliance all the way, Opera and Webkit are the new destroyers of the internet. and i say that as a Chrome user.

  • Like 1

I'm all for standards - BUT there come's a point that we need to realise that there can never be a standard that everyone is willing to adopt. It's human instinct to think "I'm better than you".

If Microsoft based IE on webkit, then we might have a chance of MAKING webkit the new "standard". I, personally, think it's our best bet. And from a developer's point of view - what do you prefer coding for? Webkit? or Trident. I know which it is for me - i've never had to put conditional comments into code for various versions of webkit like I have to on a regular basis for IE6/IE7/IE8/IE9 and no doubt, at some point, IE10.

Given that Webkit is an open source rendering engine, The argument about proprietary bits is stupid. Either open the source to Trident, or examine Webkit and build better support for those features into IE. Sounds like Microsoft are pulling an Apple here and blaming someone else for their lazy coding.

"Lazy coding"? This is about websites using proprietary WebKit CSS properties over CSS standard properties, it's in no way Microsoft's fault.

Hell, Mozilla and Opera have the same concerns, Opera now even tries to parse the proprietary WebKit rules (In case the author actually wrote the value according to the standard)

It would also help if the W3C moved a little quicker on finalizing standards. Take border radius CSS for example. The gap between the non standard prefix versions and the standards compliant version was far far to long.

What a load of rubbish.

IE10 is a superb browser and Firefox, Chrome et al need to take a few lessons from it.

Standard compliance all the way, Opera and Webkit are the new destroyers of the internet. and i say that as a Chrome user.

html5.jpg

Sorry to be the spanner in the works but Chrome still has superior HTML5 support

So what's the deal with IE6? What was so special about it? I don't understand.

It's special because it won't go away. It came out in 2001 and people still use it to this day. IE basically owned the market back then and Microsoft just sat back and let it stagnate. They didn't release IE7 until years later and only because they suddenly had competition from Firefox. Their pure laziness and greed stuck the world with a proprietary outdated browser with terrible standards compliance for nearly a decade. IE is only now becoming a good browser again, but its reputation is so badly tarnished that it may be too late to save it.

I remember when people claimed that about IE, and it was just as wrong then too.

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.

Sorry to be the spanner in the works but Chrome still has superior HTML5 support

That is indeed true but with every developer release the Chrome browser slowly becomes more and more bloated and far from what a browser should be while IE10 appears to be moving in a better direction. Of course these things are always in flux and hopefully all this healthy competition will leave us end consumes (and us developers) with a win win situation.

That is indeed true but with every developer release the Chrome browser slowly becomes more and more bloated and far from what a browser should be while IE10 appears to be moving in a better direction. Of course these things are always in flux and hopefully all this healthy competition will leave us end consumes (and us developers) with a win win situation.

That's an odd assertion because Chrome still burns through benchmarks like Peacekeeper with a score twice as high as that as IE attains, it still starts up faster, and the installation package is still nearly the same size for me (between 2010 and 2012 the download size increased by about 10 MB and that can be pretty much wholly accounted for by the inclusion of Flash and the HTML5 video decoder plugins), the binary and DLL's are pretty much the same size as ever before. The installation file for IE10 however was something like 48 MB, about 12 MB more than the Chrome installer.

It's special because it won't go away. It came out in 2001 and people still use it to this day. IE basically owned the market back then and Microsoft just sat back and let it stagnate. They didn't release IE7 until years later and only because they suddenly had competition from Firefox. Their pure laziness and greed stuck the world with a proprietary outdated browser with terrible standards compliance for nearly a decade. IE is only now becoming a good browser again, but its reputation is so badly tarnished that it may be too late to save it.

No matter how good IE 10 is and it's compliance with W3C it is plagued by the same problem. Microsoft. As long as the browser is proprietary it shouldn't be taken seriously and will continue to do damage to the web.

As noted, Microsoft should join Webkit and be done with it. Then, they can contribute to the webkit base, agree on new features with Apple and Google and everyone supports same things in the future. It would mean they would also make transparent updating to IE so it's never stagnant and have users run a different version but the latest. At that point they wouldn't even have an issue with monopoly because their browser base would be open source and would be on the same playing field with Google and Apple.

In other words they could improve it and make the web truly unified and also make developers' lives much easier.

That is indeed true but with every developer release the Chrome browser slowly becomes more and more bloated and far from what a browser should be while IE10 appears to be moving in a better direction. Of course these things are always in flux and hopefully all this healthy competition will leave us end consumes (and us developers) with a win win situation.
more and more bloated? It still feels good and I don't mind the few MB increase in the installation file.
That's an odd assertion because Chrome still burns through benchmarks like Peacekeeper with a score twice as high as that as IE attains, it still starts up faster, and the installation package is still nearly the same size for me (between 2010 and 2012 the download size increased by about 10 MB and that can be pretty much wholly accounted for by the inclusion of Flash and the HTML5 video decoder plugins), the binary and DLL's are pretty much the same size as ever before. The installation file for IE10 however was something like 48 MB, about 12 MB more than the Chrome installer.

Perhaps meaning bloated in the sense of resource usage. On my particular hardware anyway using the current official releases with a similar set of addons, Chromium typically uses 3-4 times as much memory as Firefox (at least, seen it even higher) and starts up a bit slower. Pretty much the only place where Chromium seems faster is on benchmark sites.. day to day usage, I find Firefox to be overall faster and smoother, I rarely use it but IE overall seems faster (and significantly lighter) as well on the day to day stuff.

Webkit is the standard. For both desktop and mobile. End of.

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.

Given that Webkit is an open source rendering engine, The argument about proprietary bits is stupid. Either open the source to Trident, or examine Webkit and build better support for those features into IE. Sounds like Microsoft are pulling an Apple here and blaming someone else for their lazy coding.

Sounds like you don't know what you're talking about.

  • Like 3

Perhaps meaning bloated in the sense of resource usage. On my particular hardware anyway using the current official releases with a similar set of addons, Chromium typically uses 3-4 times as much memory as Firefox (at least, seen it even higher) and starts up a bit slower. Pretty much the only place where Chromium seems faster is on benchmark sites.. day to day usage, I find Firefox to be overall faster and smoother.

All browsers with tab process isolation consume more memory than those that lack it. I'm happy to sacrifice a bit of memory usage for the knowledge that a tab crash won't completely torpedo every browser window I have open. And unlike Firefox, Chrome hasn't been plagued by memory leaks since it's inception.

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.

Chrome is the world's #1 web browser on the desktop. I'm not sure that qualifies as a "tiny share" ;) Sorry, who doesn't know what they're talking about? :laugh:

http://techland.time...nless-it-didnt/

more and more bloated? It still feels good and I don't mind the few MB increase in the installation file.

Don't get me wrong, i'm a Chrome user and it still p***** on the competition. Maybe it's in my head but it just doesn't seem as smooth as it used to.

any way the whole point of this thread is about the rendering engines and use of non standard methods of rendering content which i am all against.

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

    • No registered users viewing this page.
  • Posts

    • All these CEOs got the biggest boners thinking about firing employees for AI. Turned out it was just a wet dream.
    • And the fact that the majority of people from Poland are white European Christians while the people you are complaining about in post after post are not is just a coincidence... Every sentence in your post I am replying to is racist nonsense. None of it is actually based on any facts whatsoever. All immigrants are seeking a better life too. It's literally the only reason they would risk everything and leave their homes, families, and homeland. They are working and contributing to the economy too, as you even admit. They get the same benefits your partner did AND that YOU are eligible for as well. That is one of the key things of the EU and a mark of a civilization. That is the definition of a society where everyone is given a chance, treated equally and fairly, and is judged by the content of their character, not their different skin color or which version of ignorant superstitious nonsense their parents lied about as children. Racists around the world said the same things about the Irish and Jews and Poles (like your partner) and...every other immigrant movement over the centuries. What's your family's heritage, by the way? Were your ancestors lied about with racist fearmongering crapola by self-entitled locals the same way as you are now? If someone like that said the same things about all people from Poland, like your partner, would they be right? Or would you want them to judge your partner based on who they actually were, not where they just happened to come from?
    • Again, this is an irrelevant attempt to attack the messenger. The truth does not require any justification.
    • Removed the blue and underline as you did not post a link. This would also  be considered spamming.
    • Why it's almost impossible to produce a smartphone in the United States by Hamid Ganji If you look at the back of some Apple products, you can see the famous phrase “Designed by Apple in California, Assembled in China.” This phrase appears on products from one of the largest smartphone brands in the United States. These products are designed in the U.S., but their manufacturing takes place in China, India, Vietnam, or even Brazil. But why can’t Apple, as one of the largest American tech companies, produce its iPhones on U.S. soil? The idea for this topic came to me after the Trump Foundation launched a smartphone called the T1 and claimed that it was designed and built with American values in mind. However, this claim did not last long, as it was revealed that Trump’s phone was actually a rebranded HTC U24 Pro, with only a gold case and minor internal component changes. You see? Even a phone that is supposed to represent American values is manufactured in China. With a gross domestic product (GDP) exceeding $32 trillion, the United States is currently the world’s largest economy, while China ranks second with around $20 trillion. On the other hand, the United States is by a wide margin the global leader in various technological fields, and American companies spend hundreds of billions of dollars annually on research and development. From Apple and Google to Microsoft, Lockheed Martin, Boeing, and others, American tech and industrial giants lead their foreign competitors in many sectors. The United States also has no shortage of smartphone brands. Apple, Google, and Motorola are among the major brands in the smartphone market, collectively holding a significant share. However, the vast majority of their products are manufactured outside the United States. So why is it that the world’s largest economy, home to the most advanced technology companies and industrial powers, cannot produce a smartphone on its own soil? Let’s explore this question together. Even threats to impose tariffs won’t work After Trump entered the White House as the 47th President of the United States, his administration adopted strict tariff policies. One of these policies was the imposition of a 25% tariff on smartphones manufactured outside the United States. Trump said he “had a little problem” with Apple CEO Tim Cook over producing smartphones outside the U.S. So he thought that threatening a 25% tax on imported phones might force Apple to bring manufacturing back to the United States. “I have long ago informed Tim Cook of Apple that I expect their iPhones that will be sold in the United States of America will be manufactured and built in the United States, not India, or anyplace else,” Trump wrote on Truth Social. Image via The White House Although Apple currently manufactures some of the iPhone’s chips in the United States with TSMC's help, it still shows no willingness to shift full iPhone production to the country. At the time, renowned Apple supply chain analyst Ming-Chi Kuo wrote on X, “In terms of profitability, it’s way better for Apple to take the hit of a 25% tariff on iPhones sold in the US market than to move iPhone assembly lines back to the US.” However, manufacturing a smartphone in the United States is not as easy as it might seem, and many technical and economic barriers are involved. The lack of necessary manufacturing hubs There is a clear reason why many companies prefer to manufacture their products in China. China has established itself as the main global manufacturing hub for international companies, and over the past few decades, large contract manufacturers have emerged there, allowing companies like Apple to outsource production. One such example is Foxconn, which also manufactures some Apple products in India. Building the infrastructure required to produce smartphones in the United States would require tens of billions of dollars in new investment. Factories would need to be built, essential manufacturing equipment would have to be installed, and, most importantly, a skilled workforce capable of operating these systems would need to be recruited and trained. The United States currently lacks the core infrastructure needed to manufacture smartphones, and for this reason, many companies prefer to outsource production to Chinese contractors rather than spend tens of billions of dollars to build that infrastructure, which is significantly more economically efficient. Additionally, building such infrastructure in the United States could take up to a decade, ultimately leading to a significant increase in the product's final price for consumers. Shortage of trained labor in the U.S. compared to China Decades of serving as a global manufacturing hub have allowed China to build a massive talent pool in the production sector that is almost unmatched worldwide. Today, if a company chooses to manufacture its products in China, it can be confident that the workers involved in production have years of experience in their respective roles and are capable of producing high-quality goods with minimal errors. Even if we assume that tens of billions of dollars were invested in building smartphone manufacturing infrastructure in the United States, finding skilled workers would remain highly challenging. Apple CEO Tim Cook visiting the iPhone 6 assembly line in China in 2014. Image: Tim Cook on X In a 2015 interview on CBS’s 60 Minutes, Tim Cook said the main reason Apple isn’t producing in the US is a lack of skills. "China put an enormous focus on manufacturing, in what you and I would call vocational kind of skills. The US over time began to stop having as many vocational kinds of skills. I mean you could take every tool and die maker in the United States and probably put them in the room that we're currently sitting in. In China you would have to have multiple football fields,” Cook said. Also, in 2017, at the Fortune Global Forum in Guangzhou, Cook once again emphasized the importance of highly skilled Chinese workers. “China has moved into very advanced manufacturing, so you find in China the intersection of craftsman kind of skill, and sophisticated robotics and the computer science world. That intersection, which is very rare to find anywhere, that kind of skill, is very important to our business because of the precision and quality level that we like. The thing that most people focus on if they’re a foreigner coming to China is the size of the market, and obviously, it’s the biggest market in the world in so many areas. But for us, the number one attraction is the quality of the people,” Apple CEO said. Higher labor costs in the United States Producing almost any product in the United States is more expensive than in many other countries, and one of the main reasons is the higher cost of labor in the U.S. According to the Bureau of Labor Statistics, median weekly earnings of full-time workers in the United States were $1,235 in the first quarter of 2026. Meanwhile, the average annual salary in China's private sector in 2025 was RMB 71,590 (US$9,961). In many parts of the world, the weekly wage of an American worker is equivalent to several months of income. Another important factor to consider is that in the United States, the workforce capable of working on a smartphone assembly line is highly specialized and therefore commands higher-than-average wages. According to an estimate by Bank of America, producing an iPhone in the U.S. is technically possible, but “iPhone cost can increase 25% purely on higher labor cost in the U.S.” However, this 25% increase applies only if final assembly is performed in the United States while components are still sourced from China or elsewhere. In this case, the price of a base iPhone would rise from $799 to around $1,000. But in another scenario, if Apple were to produce the required components for the iPhone within the United States, production costs could increase by more than 90%. Trump’s dream for a “Made in the USA” iPhone might never come true In a free-market capitalist economy, one of the primary responsibilities of any CEO is to maximize profit. Using Apple as an example, Tim Cook’s role is to maximize the company’s profits so that it can fund research and development for new products and invest in areas such as artificial intelligence, while also keeping shareholders satisfied. Therefore, it is entirely understandable that Apple would choose not to bring its manufacturing back to the United States and instead keep production in countries where labor is cheaper, and products can be manufactured at a lower cost, thereby maximizing its profit margins. What is your opinion about manufacturing smartphones in the United States? If you are an American citizen, would you be willing to pay hundreds of dollars more for a smartphone made domestically in the USA? Let us know in the comments.
  • Recent Achievements

    • Conversation Starter
      jessse3334 earned a badge
      Conversation Starter
    • Reacting Well
      JuvenileDelinquent earned a badge
      Reacting Well
    • One Month Later
      Excellence2025 earned a badge
      One Month Later
    • Week One Done
      Excellence2025 earned a badge
      Week One Done
    • Week One Done
      flexorcist earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      506
    2. 2
      +Edouard
      196
    3. 3
      PsYcHoKiLLa
      153
    4. 4
      Steven P.
      72
    5. 5
      FloatingFatMan
      65
  • Tell a friend

    Love Neowin? Tell a friend!