Jump to content

Customize already installed theme on Google Chrome

Go to solution Solved by unknownmiscreant,

app data --> local --> somewhere.

Copy the directory with the theme out to somewhrer else.

Change the manifest.json file.

Enable dev mode in chrome and re-pack the extension.

Drag it into chrome to install it.

 

I did it this morning. its pretty easy.

Ok, so I have a theme on chrome that I like, all except 1 thing, which is the font color for the bookmarks bar blends into the color behind it and I would like to change the font color, I know a little bit of Java Script if I need to change the code or the Hex color in the code for the color, I just need to know where or how to access it, thanks.

Link to post
Share on other sites

app data --> local --> somewhere.

Copy the directory with the theme out to somewhrer else.

Change the manifest.json file.

Enable dev mode in chrome and re-pack the extension.

Drag it into chrome to install it.

 

I did it this morning. its pretty easy.

Sync RGB fans with motherboard RGB header.

 

Main rig:

Ryzen 7 1700x (4.05GHz)

EVGA GTX 1070 FTW ACX 3.0

16GB G. Skill Flare X 3466MHz CL14

Crosshair VI Hero

EK Supremacy Evo

EVGA SuperNova 850 G2

Intel 540s 240GB, Intel 520 240GB + WD Black 500GB

Corsair Crystal Series 460x

Asus Strix Soar

 

Laptop:

Dell E6430s

i7-3520M + On board GPU

16GB 1600MHz DDR3.

Link to post
Share on other sites

2 hours ago, unknownmiscreant said:

app data --> local --> somewhere.

Copy the directory with the theme out to somewhrer else.

Change the manifest.json file.

Enable dev mode in chrome and re-pack the extension.

Drag it into chrome to install it.

 

I did it this morning. its pretty easy.

what do you mean by enable dev mode and repack the extension and then drag it in, I got everything else done

i.e: please explain how to do these last steps

Link to post
Share on other sites

1 hour ago, SHOOK_Linus said:

what do you mean by enable dev mode and repack the extension and then drag it in, I got everything else done

i.e: please explain how to do these last steps

Right click on one of your extensions in the chrome menu --> manage extensions --> tick checkbox at the top "developer mode" --> pack extension --> point it at the directory which contains the manifest.json file. Drag the .crx file into chrome to install it. For subsequent re-packs point the second line at the .pem file that is auto created in the parent directory (same directory as the .crx output file)

 

For just testing hit you can hit 'load unpacked extension' but I prefer to pack and install each time.

 

You can change the images too. Just be careful not to make them too large, as otherwise switching between tabs is very slow in version 61.xxx and 62.xxxx 60.xxx is fine though.

Sync RGB fans with motherboard RGB header.

 

Main rig:

Ryzen 7 1700x (4.05GHz)

EVGA GTX 1070 FTW ACX 3.0

16GB G. Skill Flare X 3466MHz CL14

Crosshair VI Hero

EK Supremacy Evo

EVGA SuperNova 850 G2

Intel 540s 240GB, Intel 520 240GB + WD Black 500GB

Corsair Crystal Series 460x

Asus Strix Soar

 

Laptop:

Dell E6430s

i7-3520M + On board GPU

16GB 1600MHz DDR3.

Link to post
Share on other sites

23 hours ago, unknownmiscreant said:

Right click on one of your extensions in the chrome menu --> manage extensions --> tick checkbox at the top "developer mode" --> pack extension --> point it at the directory which contains the manifest.json file. Drag the .crx file into chrome to install it. For subsequent re-packs point the second line at the .pem file that is auto created in the parent directory (same directory as the .crx output file)

 

For just testing hit you can hit 'load unpacked extension' but I prefer to pack and install each time.

 

You can change the images too. Just be careful not to make them too large, as otherwise switching between tabs is very slow in version 61.xxx and 62.xxxx 60.xxx is fine though.

Thanks, it was saying at first that it couldn't load the extension because it couldn't find the manifest.json file but I fixed it by pointing it 1 folder forward and deleting the _metadeta folder as it was not liking it and it works fine without it. Thanks!!

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×