Is it possible to open an extensions background.js file in read mode directly from the PNaCl module (Chromium Projects Docs)? I wanted to be able to read the contents of that file, but I couldn't find any information on that topic.
Related
I just upgraded to Google Chrome v73.0.3683.103 and I am now unable to view FTP sites in Chrome. Instead of Chrome loading the FTP directory listing in the browser, it downloads a file named download which contains a directory listing.
How do I get the ability to view the FTP directories directly in Chrome back?
I have tried going into Internet Options > Advanced and clicking on the "Enable FTP folder view (outside of Internet Explorer)" but, that didn't seem to do the trick.
In-browser FTP was deprecated back in v72. I hadn't updated Chrome in a few releases. I have rolled back to v71 until I find a better workflow substitute
DETAILS: https://developers.google.com/web/updates/2018/12/chrome-72-deps-rems
I publish my extension in google web store and install it successfully in my chrome.
So I find extension's files in this directory:
C:\Users\User_Name\AppData\Local\Google\Chrome\User Data\Default\Extensions.
I use my extension for native messaging in chrome.
How do I get .crx file for publish my extension for other people without internet connections?
Or exactly like firefox *.xpi files.
Also:
If I pack extension's files in above DIR to zip and rename to crx file, and drop down to chrome this error occurs:
Package is invalid: CRX_HEADER_INVALID.
Packaging
Extensions and themes are served as .crx files. When uploading through the Chrome Developer Dashboard , the dashboard creates the .crx file automatically. If published on a personal server, the .crx file will need to be created locally or downloaded from the Chrome Web Store.
Download .crx from the Chrome Web Store
If an extension is hosted on the Chrome Web Store, the .crx file can be downloaded from the Developer Dashboard. Locate the extension under "Your Listings" and click on "More info". In the popup window, click the blue main.crx link to download it.
The downloaded file can be hosted on a personal server. This is the most secure way to host an extension locally as the contents of the extension will be signed by the Chrome Web Store. This helps detect potential attacks and tampering.
Create .crx locally
Extension directories are converted to .crx files at the Extensions Management Page. Navigate to chrome://extensions/ in the ominibox, or click on the Chrome menu, hover over "More Tools" then select "Extensions".
On the Extensions Management Page, enable Developer Mode by clicking the toggle switch next to Developer mode. Then select the PACK EXTENSION button.
Specify the path to the extension’s folder in the Extension root directory field then click the PACK EXTENSION button. Ignore the Private key field for a first-time package.
Chrome will create two files, a .crx file and a .pem file, which contains the extension’s private key.
Do not lose the private key! Keep the .pem file in a secret and secure place; it will be needed to update the extension.
Learn More
This is updated dashboard in order to download your crx file
I am developing a Chrome extension and I want to change Chrome download dir.
I searched the api list and Chrome launch arguments list but failed to find any info.
Nope, there is indeed no such API.
You can control a sub-path into the Download folder with chrome.downloads API, but that's about it.
Not many Chrome settings are exposed to extensions.
No API and launch arguments.
Finally I modify the Preferences file in profile folder.
I have a Google Drive app, which is registered as my default opener on Google Drive. This works perfectly fine when opening files using drive.google.com - When I open a file with my App, the app gets given permission to open the file and I can see that in the drive.google.com web interface.
However I recently tested this on a chromebook, and when I open a file using the Files app, I get sent to my app, however it gets a 'File Not Found' error. When I check the permissions for that file, my app hasn't been given access to it.
If I open the file using drive.google.com and then try opening using the files app again, it works since my app has been given access to the file when I opened it using drive.google.com
Seems there is a bug in the Files app on Chrome OS here, where it doesn't set the permissions to give the app opening the file permissions to access it, whereas the web interface does that correctly. Has anyone else run into this and/or should I report this as a bug to Google?
Using ChromeOS 5116.115.4 + Chrome 33.0.1750.152
This was indeed a bug, and it's fixed in the upcoming chrome 34: https://code.google.com/p/chromium/issues/detail?id=332332
I've developed extension for Chrome and I want to upload it in to Crome app store, but the issue is in that I have not only .crx file, which is needed but also some other files and dlls which should be installed in to "program files" folder.
So how can I upload my extension in to app store with .crx and some addition files?
Though I can't think of any reason why a Chrome Extension would need to install any DLLs, it is possible according to the Chrome Extension Developer FAQ. You'll end up using the NPAPI Plugin to access your DLLs, though you will need to go through an additional security review before your application gets published.