So you’ve filed a Chrome bug on crbug.com and it got fixed. Nice. But how can you know which build/release includes it? Enter CrBug Release Indicator, a Chrome extension that decorates commits on the Chromium Bug Tracker with the Chrome release number they are included in.
~
Without this extension, getting to know which Chrome version contains a certain fix is a manual and cumbersome task. Taking the now closed crbug.com/1281208 as an example – which was about unprefixing -wekbit-hyphenate-character – you need to take these manual steps:
- On the bug page, find the relevant comment that mentions a patch got merged. This typically is from an account named Git Watcher. This should lead you to Comment 11
- Copy the commit hash that is mentioned in the comment, namely
9be56a18f75dd8c20c66753946b7ff30af84a213.Alternatively, you can visit the CL page (search for “Reviewed-on”) and copy the commit hash from there.
- Look up the commit on Chromium Dash via a URL in the format of
https://chromiumdash.appspot.com/commit/$hash. This leads you to https://chromiumdash.appspot.com/commit/9be56a…a213 - On that page, finally, you can see the Chrome version numbers the CL is included in.
That’s … a lot of work, right?
~
To automate things, I created CrBug Release Indicator, a Chrome extension that decorates commits on the Chromium Bug Tracker with the Chrome release number they are included in.
Get the extension from the Chrome Web Store →
The extension essentially sniffs out the relevant comments for you on CrBug, and then uses Chromium Dash’s public API to get the version info. An example endpoint is https://chromiumdash.appspot.com/fetch_commit?commit=9be56a18f75dd8c20c66753946b7ff30af84a213. Once the data is received, the relevant info is extracted from it and gets injected into the DOM.
~
🤦♂️ While I had announced publication of the extension on X – née Twitter – last October right after creating it, I never got round to announcing it here on my blog. Blame me being busy with elbow deep into Scroll-Driven Animations.
☝️ If you’re a Googler that wants to run this extension on a corp machine you might notice that you can’t. The reason is that extensions are blocked from accessing so called “High Value Websites”. I can provide you with instructions on how to get it working, so feel free to reach out.
~
🔥 Like what you see? Want to stay in the loop? Here's how: