Every line has a story.

Chromium Context is a VS Code extension for people who work in chromium/src. Put your cursor on a line and see which Chrome release it shipped in, who can review it, and where it leads.

Install in VS Code See it work
Free. Also on Open VSX for VSCodium, Cursor and friends. Installs Git Blame alongside it.
// Copyright 2014 The Chromium Authors
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.
#include "extensions/browser/event_router.h"
#include "base/feature_list.h"
#include "extensions/common/features/feature.h"
namespace extensions {
void EventRouter::DispatchEvent(std::unique_ptr<Event> event) {
if (!event->has_listeners()) {
return;
}
DispatchEventImpl(std::string(), std::move(event));
}
} // namespace extensions

Put the cursor on a line. The status bar tells you which release it shipped in.

Click a line, or focus the editor and use the arrow keys.

Context is key.

The things you'd otherwise look up in five browser tabs, shown where you're already looking.

On the line

  • Release milestoneIn the status bar, for whatever line the cursor is on. Click for the CL; double-click for Chromium Dash.
  • Code SearchOpen the line on source.chromium.org, copy its URL, or copy a tiny crsrc.org path for chat.
  • Terminal links../../path:line and Foo::Bar in build output become clickable.

In the file

  • BUILD.gn and //pathsDeps and paths turn into links you can follow.
  • Related filesJump from a file to its tests and back.
  • Code ownersWho can approve this file, and how quickly they usually do.
  • Small conveniencesTODO list, mojom, IDL and GN language modes, C++ snippets, and a command that turns ALL_CAPS constants into enum class values.

Across the checkout

  • GerritYour open CLs and the ones waiting on you, each tagged with its milestone.
  • Tree statusWhether the tree is open, before you land.
  • .crx and .zipOpen extension packages right in the editor.
  • Stack tracesImport a crash stack and walk it frame by frame.

Who can review this, and how long it might take.

Code Owners lists everyone who can approve the file you're editing, with their median turnaround. Look up anyone else by email. One click opens the CLs already in their queue.

Run the test you're reading.

The Tests view finds gtest cases in the open file. Run one in place with a command you control, copy its filter, or export the list. When a test flakes on one platform, Disable writes the MAYBE_ block for you.

Run command (default)
autoninja -C ${out} chrome ${target} && xvfb-run ${out}/${target} --gtest_filter=${test}
Test: Disable
#if BUILDFLAG(IS_MAC) #define MAYBE_OpensPopup DISABLED_OpensPopup #else #define MAYBE_OpensPopup OpensPopup #endif

Open a checkout.
Watch the status bar.

It works the moment VS Code opens a folder with chromium in its path. Nothing to configure first.

Install in VS Code Get it on Open VSX
Installed 37K times from Open VSX and 6.9K times from the VS Code Marketplace. Version 0.4.6.
📜 Documentation 🐞 Report a bug 👀 Read the unminified source