What is Recent Crbugs?
Recent Crbugs is a productivity chrome extension. it's a free extension , it has 102 active users since released its first version, it earns an average rating of 2.50 from 2 rated user, last update is 3278 days ago.
What’s new in version 1.3.1?
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)
How to install Recent Crbugs?
You could download the latest version crx file or older version files and install it.
Preview of Recent Crbugs
Technical Features:
- Latest Version: 1.3.1
- Requirements: Windows Chrome, Mac Chrome
- License: Free
- Latest update: Thursday, May 21st, 2015
- Author: jleichtling
Recent Crbugs Available languages:
English.
FAQ
-
What about others talk about recent crbugs chrome extension?
50% user give 3-star rating, 50% user give 2-star rating. Read reviews of recent crbugs
-
How could i get help if there is something wrong with recent crbugs chrome extension?
You could find more help information from recent crbugs support page.
-
How could i contact the developer of recent crbugs chrome extension?
You could send emails to publisher, or check publisher's website.
-
What are the required permissions for extensions?
- webNavigation
- storage
- clipboardWrite
- https://code.google.com/*
More about manifest_file of recent crbugs.
-
How could i report abuse of recent crbugs chrome extension?
You could click to report abuse of recent crbugs.
Reviews of recent crbugs:
??????
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.