[Question] The original was updated 2019 Oct 13! What now?

[apollolux]

Hello! Due to security policy at work we're stuck with the original CJS on the office-wide extension whitelist instead of the much better CJS2 which I use on a personal comp . What I've done on my office comp install is customize it to my personal liking, which doesn't persist because every time Chrome opens it then considers the extension "corrupt" and I have to re-install it then copy my edited version of the files, but that's neither here nor there. Because of the whitelist I often check if there are alternatives to original CJS that are allowed by the policy, but also action is taken regarding extension updates as they are automatic.

I found yesterday that a version 2.2.5 of the original CJS has been posted to the store and made available 2019-10-13. A cursory glance of its source seems to reveal no significant difference to the previous 2.2.4 version from 2018, but maybe I just wasn't looking hard enough. What are your thoughts on this updated version, and if it indeed had any improvements that I didn't notice how long before we can see them in CJS2 if they're not already there?

Thanks in advance for taking the time to consider giving your take on the "new" CJS. and thanks for taking the time and effort to update and maintain a much improved version of the thing that is an actually useful lightweight alternative to TamperMonkey on Chrome!

+Alex Rosario, a developer

[xcv58]

I will take a look of the original one.

[xcv58]

@apollolux thanks for letting me know this.

I didn't see any significant improvement from the v2.2.5. I tried to contact the original author of Custom JavaScript for Websites to see whether we can collaborate together.

[xcv58]

@apollolux exciting news, I find the original author: Dan https://twitter.com/junkycoder. I invited him to discuss the future plan for the extensions.

[junkycoder]

Hey guys, glad @xcv58 found me. I'd like to open CJS development again. The last update I made was just change of browser icon, so no new features - sorry. Next week I'd like to go throw issues and collected knowlage here and discuss the future of CJS with you.

[junkycoder]

Mean while, @apollolux have you chance to install chrome extension manually (chrome://extensions)? Mby you can just download the ZIP of CJS2 and install it to your office computer..

[apollolux]

Hello @junkycoder & @xcv58 ! Sorry for the late reply, I missed the notification. I am unfortunately unable to install extensions manually at work due to the group policy. The "developer mode" toggle in chrome://extensions is essentially just for show in here as a result.

Also, as of Chrome 76 (I think, might have been 77 or 78 instead) any extensions that I customize while the browser is open are instantly flagged as "corrupt" and prompt to reinstall them. I mention this because as a workaround I was customizing my install of CJS to change the look of my copy and attempt to add more functionality like custom CSS a la Stylish/Stylus (because neither of these two are whitelisted here) and global custom JS a la TamperMonkey/ViolentMonkey, but was unfortunately unable to rewrite the hooks to include extra code because when the browser is open it only runs certain hooks when the extension is "activated" and deactivating then reactivating the extension to run the rewritten hooks triggered the corruption flagging.

CJS is still a useful extension regardless of Chrome's current shortcomings and I'm glad it's in the company's whitelist. :)

[xcv58]

Also, as of Chrome 76 (I think, might have been 77 or 78 instead) any extensions that I customize while the browser is open are instantly flagged as "corrupt" and prompt to reinstall them. I mention this because as a workaround I was customizing my install of CJS to change the look of my copy and attempt to add more functionality like custom CSS a la Stylish/Stylus (because neither of these two are whitelisted here) and global custom JS a la TamperMonkey/ViolentMonkey, but was unfortunately unable to rewrite the hooks to include extra code because when the browser is open it only runs certain hooks when the extension is "activated" and deactivating then reactivating the extension to run the rewritten hooks triggered the corruption flagging.

Could you please share more information like operating system and Chrome version so that I can try to reproduce it? And it would be great if you have any log message that can share it here without breaking your company policy.