I have a chrome extension whick among other things is replacing the new-tab functionallity.
But since i can't restore all the new-tab functionallity (account sync login,bookmarks,web apps,recent sites,most popular).
I want the users to be able to restore the default new tab, w/o uninstalling my extension.
From my investigation there is the internal chrome scheme: "chrome-internal://" whick has the URL : chrome-internal://new-tab/ .
When i try to navigate to it from my extension it does not seem to work (premission denied,although i requested it within the mainfest).
But when navigating to it from chrome (js console) it does show the default new tab.
Any help will be appreciated.
In a Chrome extension, you can set a tab to display the original chrome new tab page by calling update on it:
chrome.tabs.update({
url: 'chrome-internal://newtab/'
});
The "New Tab" chrome extension does this. View the code on GitHub.
Alex is right. from Chrome 33+
https://www.google.co.jp/_/chrome/newtab?ie=UTF-8
replace chrome-internal
and chrome://apps works.
Related
I published my chrome extension to the store a couple of hours ago and received the message: "Your item has been published. All changes will take effect within a few minutes." and am yet to see it appear in the store (still seeing this message).
Does it usually take this long for a chrome extension to show up in the store?
When I click "View in Chrome Web Store" link in the new Developer Dashboard I get to https://chrome.google.com/webstore/detail/************************/publish-accepted-testers?authuser=0&hl=en page:
But if I click on the extension name in the old Developer Dashboard I get to https://chrome.google.com/webstore/detail/extension_name/****************** page where Add to Chrome button is active.
If you go to the webstore developer dashboard, you should be able to click on your extension, that will bring you to its webstore page. You can share this link before your extension gets listed, which often takes a few hours.
I ran into this issue, and needed to revert to the old developer dashboard (as #Winand mentioned) to get to the correct link in the web store. Here's a screen shot of how to opt out of the new Chrome Extension Developer Dashboard:
More info on the Chromium blog here: https://blog.chromium.org/2020/03/new-developer-dashboard-and.html.
close the the browser and restart it.If still getting prob then go and try again to the more tools and extension .Search it over there ,if enable then restart & use it.
For the life of me I can't find where to enable this setting: Override requests with workspace project in Chrome Canary v64.0.3
Where do you enable this feature?
I learned about this feature from here: https://umaar.com/dev-tips/162-network-overrides/
Currently with 65 Chrome Canary it's not experimental anymore.
But you still cannot "Save for overrides" XHR requests.
This restriction is only in UI. To get XHR request override:
Open "Sources tab" in Chrome Canary DevTools and "Overrides" sub-tab under it.
Check "Enable Local Overrides" and add a folder to store changes in the filesystem.
Open "Network" tab in Chrome Canary DevTools and select XHR request
Press "Open in new tab"
Go to new opened tab Chrome DevTools - "Network"
Select the first request in the list and "Save for Overrides" button appears.
You can follow the gif from question starting step 5:
It's behind an experiment (https://developers.google.com/web/tools/chrome-devtools/ui#experiments) then it'll be under experiments in the settings panel of devtools.
Please do be warned though, this is an experimental feature, there are bugs and it might not work as intended.
We are trying hard to get it fully released soon (on Canary) but it needs to be a 1st class feature before we will feel ready to release it.
I think they might have shipped the feature, so it's no longer behind an experiment.
Try the workflow that Umaar outlined, omitting the step about enabling the experiment.
Haven't tried it myself yet, so I could be wrong
The feature is no longer an experiment in Chrome Canary (current version at the time of this: 64.0.3261.0). You can start to use it now. It will take a little time to arrive in Chrome stable.
In the latest version of Chrome Canary (Version 65.0.3317.2) you still need to enable dev tool experiments. The option is still behind the experiment flag #kayce-basques . I also followed the tutorial of Umaar - also using GitHub for testing - but I don't get any visible website changes after pressing F5.
Has someone figured out how to get it to work?
(1) Select the Overrides Tab in the Sources Panel.
(2) Click the Setup Overrides ( + icon) to add an empty folder.
(3) Confirm that Enable Network Overrides are enabled.
(4) Select the js file to be persisted on the Network Tab and display the source code in the code editor.
(5) Add code “console.log (‘hello world’);” to the beginning of the source code.
(6) Right click on the source code, select command [Save for overrides] on the context menu.
(7) Reload the current page after saving the file.
(8) Open the Console Panel and check the result.
This feature is now enabled in chrome stable you can follow these step:
In chrome go to "Sources tab" then in devtools "Overrides" click "Enable Local Overrides" then create a folder to put the changes in the filesystem. Go to
"Network" then select XHR request then "Open in new tab" then go to new opened tab Chrome DevTools - "Network"
pick the first request in the list and normally you will have a "Save for Overrides" button appears.
I created and uploaded a Gmail extension to the Chrome Store and have been trying to test it. I deleted it from my extensions list in Chrome and when I went to go re-download it from the Web Store it said "Added to Chrome" and would not let me re-download it. I found a few solutions that described how to delete cached data on a PC, but I'm using a Mac. Any ideas?
I'm a total newbie at this so any help would be appreciated. Also not a very strong Mac user. Thanks!
Try to restart your Chrome browser, if the extension still not exist, reset the chrome settings to default, you need to do this if apps or extensions you installed changed your settings without your knowledge. Your saved bookmarks and passwords won't be cleared or changed.
Open Chrome.
In the top right, click the icon menu
Click Settings.
At the bottom, click Show advanced settings.
Under the section "Reset settings,” click Reset settings.
In the box that appears, click Reset.
The kitchensink example is working fine in my Chrome browser
http://cdn.sencha.io/touch/sencha-touch-2.1.0/examples/kitchensink/index.html#demo/jsonp
But when I downloaded the code of it and run on local server, it remains in state of data loading.
Its because of cross-origin errors you get in the javascript...
Go to your chrome shortcut -> right click -> properties -> shortcut
Change the target field from:
"C:\Users\boris.d\AppData\Local\Google\Chrome\Application\chrome.exe"
to
"C:\Users\boris.d\AppData\Local\Google\Chrome\Application\chrome.exe --allow-file-access-from-files"
and it will work for you :-)
add JSONView as extension in your chrome browser and refresh your page.It will work.
use following link to add:
https://chrome.google.com/webstore/detail/jsonview/chklaanhfefbnpoihckbnefhakgolnmc/related?hl=en
I'm trying to use the Chrome Experimental Devtools API.
I've tried running Chrome with: --enable-experimental-extension-apis as suggested here: http://developer.chrome.com/extensions/experimental.html and enabled the "Experimental Extension APIs" in the flags settings.
When I open the Console in Chrome (or Canary), I get the following:
chrome.devtools: undefined
chrome.experimental: undefined
I'm running Chrome 21.0.1180.77 beta-m. I've also tried Canary.
What am I missing?
As explained here: http://developer.chrome.com/extensions/devtools.html, the chrome.devtools APIs are only available in your devtools HTML page.
First, you need to create an HTML file and then add it to your extension's manifest under the "devtools_page" key. When you load your extension into Chrome and open the DevTools, you should see your new tab.
In that tab is the only place chrome.devtools will work.
chrome.experimental is different and will be available in all of your background pages and content scripts.
You need to run it only in Canary.
Plus when you run chrome add this flag to the command line:
path_to_chrome.exe --enable-experimental-extension-apis