This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 973
Vimium: Icon not displayed near address bar #6193
Milestone
Comments
4 tasks
@jonathansampson do we need QA for this issue, or is this postponed until Vinium extension becomes ready? |
luixxiul
added
the
needs-info
Another team member needs information from the PR/issue opener.
label
Feb 16, 2017
@luixxiul The root issue is resolved; this is good closed :) |
This was referenced Mar 3, 2017
Reopening as |
luixxiul
added
QA/test-plan-required
and removed
needs-info
Another team member needs information from the PR/issue opener.
QA/no-qa-needed
labels
Mar 5, 2017
This was referenced Mar 17, 2017
This was referenced Mar 28, 2017
Added no-qa-requried as the extension is not available in packaged build for testing |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Test Plan:
An extension's manifest file may contain a
browser_action.default_icon
property. This property usually holds an object, but may (in older extensions) hold a string. String paths to images were not being handled by Brave, which caused some extensions (such as Vimium) to have no displayed icon.To test this, install the Vimium extension in your development build of Brave. Vimium's extension ID is dbepggeogbaibhgnhhndojpepiihcmeb. With this extension registered and loaded, running Brave should reveal the Vimium icon near the Brave Shield icon.
This commit also prevents the redundant look-up of
manifest.browser_action.default_icon
(path
is already a reference tobrowser_action.default_icon
). Also,manifest.icons
should not be the source for browser action icons.Original issue description
Describe the issue you encountered:
Upon loading the Vimium extension, there was no icon displayed near the address bar.
Work-around:
Adding the following (borrowed from
manifest.icon
) to themanifest.browser_action
object resolves:Brave Version: 0.12.15
The text was updated successfully, but these errors were encountered: