Recent Crbugs

Quickly access crbugs you have recently viewed.

Recent Crbugs Chrome Extension

Recent Crbugs is a Chrome extension that allows you to quickly access crbugs you have recently viewed. It enables you to search crbug.com, filter crbugs by search, and provides a larger click target. With Recent Crbugs, you can easily access and manage your crbugs without hassle.

Download

Extension stats

By: jleichtling

Users: 65

-8

Rating: 2.50

(2)

Version: 1.3.1 (Last updated: 2015-05-22)

Creation date: 2015-05-21

Risk impact: High risk impact

Risk likelihood:

Low risk likelihood

Manifest version: 2

Permissions:

webNavigation
storage
clipboardWrite
https://code.google.com/*

Size: 499.71K

Ranking

# 78,674 ▼ 1,317

Other rankings

#31397 in Workflow & Planning ▼ 216 #223 in suggestion keyword 21 ▼ 17

Other platforms

Recent Contacts (v2.0.2)

2.13

(96) 22,829+

Not available on Firefox

Not available on Edge

Want to check extension ranking and stats more quickly for other Chrome extensions? Install Chrome-Stats extension to view Chrome-Stats data as you browse the Chrome Web Store.

Extension summary

Analyze keywords

Go ahead. Close that crbug tab. You know it's just two clicks away.

New in v1.3.1:

Fixed bug where long titles caused copy button to be pushed off the right side of the popup

New in v1.3:

Search crbug.com
Larger click target (thanks scheib@ for the suggestion)

New in v1.2:

Filter crbugs by search
New and improved UI (thanks ainslie@ for the good suggestions, thanks to me for the ones I butchered)

User reviews

👎👎👎👎👎🙏

Masoud Shokohi (Mass59), 2022-03-06

It used to work and it was great, but now it only display a few bugs. If I right click on the extension button and select "Inspect popup", all the bug are displayed and I see a javascript error: Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'self' chrome-extension-resource:". I think the bug display because when the javascript console is opened all security errors are ignored. My guess is that the error cause the failure to display the bugs.