Here are a few search strings, each of which links to its corresponding Google search results page:



javascript split


fillRect context

Scan through the results.

You’ll find Mozilla Developer Network pages in the top few positions on just about every search. Which stands to reason.

You’ll find Microsoft Developer Network pages up high, too. Which stands to reason.

And for that last search string, a Dev.Opera page occupied the top slot in my search results. Not too shabby, considering Opera’s desktop browser market share: less than 2 percent.

What’s conspicuously absent?

Let’s try a few more searches:

Chrome developer offsetTop

Chrome developer getElementsByTagName

Chrome developer javascript split

Chrome developer hasOwnProperty

Chrome developer fillRect context

You’ll notice the top slots are mostly occupied by StackOverflow questions.

Don’t expect much of a difference if you substitute “Safari” or “webkit” for “Chrome.”

Oh Chrome, where art thou?

Yes, it appears that of the Big Three browser makers (in terms of market share), two have high-ranking developer networks that document the functions/methods/etc. of client-side code running in their browsers. The other just doesn’t seem to have a presence.

Could this be merely a temporary result of the Chrome team having been punished by Google for its shenanigans involving paying for link juice? Not likely. We can infer that the 60-day penalty period, during which Chrome was demoted in Google’s search results, is over based on the fact that a search for “browser” shows Chrome in a top slot, right below Firefox.

No, the reason you don’t see any official Google/Chrome documentation pages showing up for these search queries is because there basically isn’t any Google/Chrome equivalent to the MDN and MSDN.

So I suppose the question is: Does there need to be?

Google may consider the differences between Javascript in Chrome and Javascript in Firefox so minor that it’s content letting the MDN documentation essentially speak for both of them — why reinvent the wheel?

Well, one reason to reinvent the wheel is to promote its product. Put out quality Javascript documentation on a Chrome developer site, and you’re going to be promoting Chrome, just the same way that Mozilla is promoting Firefox with its JS documentation.

But maybe the Chrome team thinks that other ways of promoting its product will yield higher returns.

What do you think?