Updating our component extensions w/o updating browser

260 views
Skip to first unread message

Asesh Shrestha

unread,
Dec 6, 2017, 4:05:51 AM12/6/17
to Chromium-dev
Hello, I have been researching on how to update our component extensions which is bundled with our browser w/o updating browser. Till now, we have had to update our browser, if we make any changes to our component extensions. Looks like Chromium does support updating component extensions which I found out by going through the files in this folder: src\components\component_updater. We have our own couple of component extensions which is part of our browser but after debugging, looks like those component extensions won't be in 
the list of updates to be checked. I know, I will have to modify URL for updating component extensions too which we are planning to do too. 

When I go to this URL: chrome://net-internals/#modules

ahfgeienlihckogmohjhadlkjgocplebfalsetrueWeb Store0.2Discover great apps, games, extensions and themes for WorkStream Browser.
ddmbapcgpfbnlhildjojbgcgcefninddfalsetrue
1.1
ddpcfofnhhgnhahaghledkiehmlhokjgfalsetrue
2.0.1
eemcgdkfndhakfknompkggombfjjjenofalsetrueBookmark Manager0.1Bookmark Manager
ehjpllolcojjdjnmoobagehfbclhpdkffalsetrue
1.2.2
kmendfapggjehodndflmmgagdbamhnfdfalsetrueCryptoTokenExtension0.9.46CryptoToken Component Extension
mfehgcgbbipciphmccgaenjidiccnmngfalsetrueCloud Print0.1Cloud Print
mhjfbmdgcfjbbpaeojofohoefgiehjaifalsetrueChromium PDF Viewer1
oaijfofffpkkchogoakdicnnhkajbmpifalsetrue
1.0.0.0
pfmgfdlgomnbgkofeojodiodmgpgmkacfalsefalse
3.1.0
pjckickhkkmapdlmgcakhflbmbnhfommfalsetrue
5.0.1

I have removed description and name for security reasons.  I can see our component extensions too but those extensions aren't included when checking for updates. Now, below is the screenshot which only checks for updates for a few component extensions and none of them are listed above.


I can barely find anything on Google, so am trying to find out by debugging. Can someone give me a pointer on how to update component extensions and how can our custom component extensions be updated?

Thanks

Marc Treib

unread,
Dec 6, 2017, 5:21:18 AM12/6/17
to asesh.s...@cloudfactory.com, Chromium-dev
Note that there is a difference between Components and Component Extensions. Confusingly, both ship with Chrome, and both come in the form of .crx files, but it looks like the component updater only handles Components (the non-extension variant).
I don't know how Component Extensions get updated, maybe that just happens along with regular extension updates?

”This email and any files transmitted with it may be confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender.”

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/9b6a07f5-2a41-4997-90b2-ae30020db1b7%40chromium.org.

Joshua Pawlicki

unread,
Dec 6, 2017, 11:28:53 AM12/6/17
to Chromium-dev, asesh.s...@cloudfactory.com, R.Devlin Cronin
Devlin can correct me if I'm wrong, but I don't believe component extensions get updated except as part of the browser release. As Marc says, the component updater is something different.
Have you looked into deploying your software as default extensions instead?


On Wednesday, December 6, 2017 at 2:21:18 AM UTC-8, Marc Treib wrote:
Note that there is a difference between Components and Component Extensions. Confusingly, both ship with Chrome, and both come in the form of .crx files, but it looks like the component updater only handles Components (the non-extension variant).
I don't know how Component Extensions get updated, maybe that just happens along with regular extension updates?

Asesh Shrestha

unread,
Dec 6, 2017, 11:44:59 AM12/6/17
to Chromium-dev, asesh.s...@cloudfactory.com, rdevlin...@chromium.org
Those extensions must be bundled as component extensions because we don't want our users to remove or disable them. Well, if that's the only way to update component extension then that's fine :|

BTW, like Marc said, I got confused between them.

Thanks a lot guys for replying :)


On Wednesday, December 6, 2017 at 10:13:53 PM UTC+5:45, Joshua Pawlicki wrote:
Devlin can correct me if I'm wrong, but I don't believe component extensions get updated except as part of the browser release. As Marc says, the component updater is something different.
Have you looked into deploying your software as default extensions instead?

On Wednesday, December 6, 2017 at 2:21:18 AM UTC-8, Marc Treib wrote:
Note that there is a difference between Components and Component Extensions. Confusingly, both ship with Chrome, and both come in the form of .crx files, but it looks like the component updater only handles Components (the non-extension variant).
I don't know how Component Extensions get updated, maybe that just happens along with regular extension updates?

Reply all
Reply to author
Forward
0 new messages