6

In all browsers I tested (IE, Firefox, Chrome, Safari, Opera, Yandex), window.navigator.appCodeName returns "Mozilla". I know the history of web browsers "hijacking" the user agent to fool pages into thinking that they are compatible with all other browsers, and I was content to live with appCodeName just being an extension of that principal, however, I read the standard, and it turns out that the standard itself says that this will be the hardcoded value "Mozilla". So all these browsers are actually following the standards.

Why does this value exist? I assume it's reserved for future use, but what is the plan?

This question doesn't really explain it, because all it states is that it was because browsers hijacked it, which I already understand, but I'm moreso wondering what the past or future use was/is.

rink.attendant.6
  • 44,500
  • 61
  • 101
  • 156
LadyCailin
  • 849
  • 10
  • 26
  • and IE11, Chrome, Firefox, and Safari return appName "Netscape" :) – Petroff Jun 15 '15 at 16:50
  • I reread your question, and I agree that it isn't quite the duplicate I thought it was. Sorry about that. – BoltClock Jun 15 '15 at 18:19
  • Unfortunately I don't think there's any documented history of appCodeName and why exactly it was created at the time. This stuff dates back to the mid-90s. – BoltClock Jun 15 '15 at 18:43

2 Answers2

3

From NavigatorID.appCodeName - Web API Interfaces:

The NavigatorID.appCodeName always returns 'Mozilla', on any browser. This property is kept only for compatibility purposes.

Note: Do not rely on this property to return a real product name. All browsers return "Mozilla" as the value of this property.

This is similar to NavigatorID.product, which always returns the string 'Gecko'.

As Sebastian G. explains in his answer, it was used for user agent sniffing. This implies that at some point in time non-Mozilla browsers did not contain Mozilla in its UA string. Though I'm not sure how long the period of time was between Mozilla/Mozilla-based browsers had "Mozilla" in the UA string and the addition of "Mozilla" in non-Mozilla browsers.

I can't find any documentation on when the appCodeName property first became available in the navigator object (presumably before 2000, as it was referenced in 2000 as "ages ago").

This article might be of interest to you: Agent Strings in Popular Browsers

Community
  • 1
  • 1
rink.attendant.6
  • 44,500
  • 61
  • 101
  • 156
  • Yes, I noticed there were a couple of similar values. What was the purpose previously? Have all browsers always used the value "Mozilla", or have there been other values in the past? – LadyCailin Jun 15 '15 at 18:01
  • I believe all browsers (with the possible exception of some really obscure ones) used the value Mozilla, as they were either actually Mozilla-based or pretended to be Mozilla. – rink.attendant.6 Jun 15 '15 at 18:03
  • If the value has always been "Mozilla" in all browsers, then how could that have ever been a used value practically? What would the "else" statement be? if(mozilla){ showContent(); } else { neverRuns(); } – LadyCailin Jun 15 '15 at 21:22
  • Ah, so there could have been a point where appCodeName wouldn't have been "Mozilla", at least, for a short time. – LadyCailin Jun 15 '15 at 21:27
  • excellent article you shared ("Agent Strings in Popular Browsers") – mishal153 Feb 25 '16 at 14:08
2

The war between browsers

It's a historical and compatibility purpose.

It all began when the first browsers appeared. Soon the battle of feature-implementation began (which isn't over after all). They wanted the developers to use their browser.

Because feature-detection wasn't a thing back then, browser-sniffing was the hot method to detect if a feature could be use. So developers sniffed around and implemented nice new features only for a specific browser. But then the other browser-vendor also implemented that feature, but the users didn't see it, because it wasn't a 'Mozilla' (for example).

The solution? Users of a non-Mozilla browser should also see that nice little feature and use the website as intended - so they all began to lie.

That's pretty much it in a nutshell. It's not reserved for future plans, but for past content access. And it's still like this, because the web is designed to last. So today you can visit a really old website and get all the information and features like in the old days.

Original Purpose

The property's purpose in first place was the representation of the internal code name of the browser (like 'Lollipop' for Android 5). Mozilla was one of the first ones to implement it - probably as an API for JS-Developer to explore or for their own scripts. And it was intended to represent the code name of each browser individually. But as mentioned, history took another path.

Sebastian G. Marinescu
  • 2,374
  • 1
  • 22
  • 33
  • 1
    "because the web is designed to last. So today you can visit a really old website and get all the information and features like in the old days." that is beauty right there :) – mishal153 Feb 25 '16 at 14:13