I am looking for a way to detect, within an extension, if a Chrome browser install CAN be opened in Incognito mode: I need to find the value of IncognitoModeAvailability.
I am not looking to find out if the browser IS in Incognito mode. Nor am I looking to find out if the extension will work in Incognito. Nor am I trying to make an extension work in Incognito.
I'd like the Chrome extension to be able to detect if the Chrome browser install even HAS an incognito mode as a possibility. Having trouble finding anything that speaks to this.
Any assistance is appreciated!
I used to use Firefox and the beloved plugin Firebug to work with web pages, since you can edit the HTML-code, and see the result on the page as you edit it.
The last version to support this and firebug was Firefox 49, and all newer Firefox, Chrome and Safari version doesn't have this. You can edit the code, but you have to click outside or CMD/CTRL-Enter to confirm the changes.
Why isn't this implemented in newer browsers, it doesn't seem that complicated, and it's so useful. I can't believe I can't find anyone else discussing this on the Internet.
Is there any browser version and/or plugin to Chrome that can do this?
Thanks!
As far as I know, no browser allows this and there isn't any extension for that, unfortunately.
Though there is a feature request for the Firefox DevTools asking to add live editing.
When I try to create an instagram client (developer side), I'm always getting the same error:
Captcha invalid, please try again
Submission error: please fill out all required fields.
All fields are correctly set and captcha is good. (I tried many times, but always same error)
Someone have a solution for me?
If you look at the console, we can see there is an error related to "Content Security Policy" which avoid loading google captcha script :
Based on this answer there is no easy way to disable "Content Security Policy" in Chrome except by using an extension.
Such an extension is available here : Disable Content Security Policy [Google Chrome extension]
Once the extension is active, the instagram form loads without errors and should look like this :
For security reason I highly recommend to uninstall the extension once the app is created.
I am getting the same errors, tried different browsers and even computers, no luck. I think its broken for everyone...
Edit: To clarify this is the form with the broken Captcha https://www.instagram.com/developer/clients/register/ and seems to prevent any new clients from being created.
Edit2: Tried the following devices
Win10 w/ Chrome v61.0.3163.100
Android 7.12 w/ Chrome v61.0.3163.98
SUCCESS: Worked only on a MacOS(Sierra 10.12.5) with Safari. Tried with Chrome v60.x and still did not work on the Mac. Only Safari seems to work.
Just go to your Google Chrome in your mobile phone (mine is Android) and it should work.
It worked for me ;)
Well. I found a solution.
I had the same problem. Simply do that from your cellphone and it works.
Update: The Android Chrome version that I used is: 61.0
https://www.instagram.com/developer/clients/register/
This form is broken, throws below error:
The captcha solution was not correct. Please try again.
Submission error: please fill out all required fields.
For those who just want the access the api and dont need a client id this is a workarround.
I mangaged to get an access_token through http://instagram.pixelunion.net/
So i can still load images from my profile on my site
https://api.instagram.com/v1/users/{userid}/media/recent/?access_token={generated_accesscode}
It worked for me in a Incognito window in Google Chrome
The captcha doesn't event show up for me on any browser on OS. Mobile or desktop. In the end I just didn't use a client ID and the user Id and access token seem to be enough for me to access my feed.
https://codeofaninja.com/tools/find-instagram-user-id
http://instagram.pixelunion.net/
You have to press enter after typing your redirect_url.
Don't just click or tab to the next field.
I solved this issue by inserting a longer value in the description form input and by using the Firefox browser... What a joke !
I don't understand the matter but it's the only way I found.
I hope it will help someone here.
I tried Android app, Android Chrome, Android Firefox, and Laptop's Chrome. None of them worked... Finally I tried Laptop's Firefox and it worked like a charm... I happened to get a captcha with 3 words. Actually it was 2 signs but the second one has a road name and a number.
It works on latest version of firefox (v 55.0.3 32-bit) for me on windows 8.1.
Tried on android chrome, but that would not even let me open instagram.
I just finished creating couple of applications.
It worked for me using Chrome on macOS High Sierra. Chrome version is 61.0.3163.100 (Official Build) (64-bit).
Worked immediately on Firefox without a hiccup.
Firefox:55.0.3 (64-bit)
OSX Sierra: 10.12.6 (16G29)
Didn't work on Safari or Chrome.
Hope it works for you.
I tried different OS (Windows/Linux/Mac OS/iOS/Android) and browser (Chrome/Safari/Firefox/IE) combinations with absolutely no luck. I contacted instagram and reported this issue and I recommend you do the same.
In the meantime, I found this temporary workaround. I went ahead a generated an access token using this link: Instagram Pixel Union
Now I can continue doing the development work while waiting for the response from instagram. I also sent the request to them for information
I got the form to successfully submit the first time round using Mac OS Sierra 10.12.6 in Firefox 54.0.1.
No version of Safari or Chrome would work for me.
Had the very same error:
The captcha solution was not correct. Please try again.
Submission error: please fill out all required fields.
Hope Firefox solves the issue for all.
We are automating chrome extension with sahi.
we have loaded our chrome profile with sahi with extension added on profile.
we weren't able to get dom elements of extensions.
so we are navigating to the url: chrome-extension:/extension_id/popup.html
but sahi doesn't navigate to this url.
but i have read with selenium we are able to get it.
Please help me out, with this automation
I'm not sure, I understand the problem here. But if you want to change some options on chrome. I use this Chromium Command Line Switches to find correct option to set when set browser on 'browser_types.xml`.
For example:
<options>--no-default-browser-check --user-data-dir=$userDir\browser\chrome\profiles\sahi$threadNo --proxy-server=127.0.0.1:$port --disable-popup-blocking --always-authorize-plugins --allow-outdated-plugins --enable-npapi --incognito</options>
Google Drive 301 redirect problem in both Internet Explorer 9.0 and Google Chrome.
How to download and recover my documents back?
Error details:
The webpage at https://docs.google.com/nonceSigner?nonce=7cb3t4occcafo&continue=https://doc-14-bg-docs.googleusercontent.com/docs/securesc/i5n0sn4aobda0j320f46k73eteiillh3/plshk64l31ed2qevsqk23j88fdobcn2g/1342972800000/16921087564105121353/16921087564105121353/0B4IwZnOWxZeUMUdqOG9iU2dRT3VGMm82aDdWNUV3QQ?e%3Ddownload%26hash%3Dhhjr1n96p6fbnep6l9cudvmg5ec7jr43%26nonce%3Db1573nhruskb0%26user%3D16921087564105121353&hash=f23l5btt5380bvi1fh63om23i6m3t5t4 has resulted in too many redirects. Clearing your cookies for this site or allowing third-party cookies may fix the problem. If not, it is possibly a server configuration issue and not a problem with your computer.
Here are some suggestions:
Reload this webpage later.
Learn more about this problem.
I have experienced this in Chrome, IE, and Firefox when trying to download files from Google Drive. Disabling extensions & incognito didn't solve this for me, but I was able to find a workaround by using the Google Drive Desktop app.
https://tools.google.com/dlpage/drive
Hope that helps!
Based on a hint on cookies on Google forums, I found a solution:
By allowing Google to set cookies, the problem disappeared for me. Chrome settings > Advanced > Content settings ... > Cookies > Manage exceptions. Allow:
https://[*.]google.com:443
https://[*.]googleusercontent.com:443
The rule could be more specific but this works. I hope this helps. I had non-default cookie restrictions.