My app is served on localhost. I am testing it on Browserstack: see title for browser version and OS. I'm running Chrome 59 on OSX Sierra.
I've tried entering localhost:PORT, and http://localhost:PORT but am always given a Bing search result for that string, instead of directing to my development server. I know the server is up because I'm doing manual testing on Firefox, Safari, and Chrome.
I've also attempted to change Edge settings in guides like this one, but there the button to remove bing completely does not exist.
Can anyone point me at support/docs that disable this functionality? Thanks!
Related
I am using browserstack to test some devices, like IE. However I need to set up local testing so I can test my site localhost:3000
I have logged in to browserstack in Chrome and installed the extension. I click on the extension IE11 link. It takes me to a IE11 on Windows 8 virtual machine.
I type localhost:3000 into IE but it doesn't seem to work.
Then I click the Settings cog and click resolve all URLs through my network.
Still it doesn't seem to work for me.
Looks like the setup was fine in Browserstack, I just forgot that in IE11 I need to use http://localhost:3000 as it doesn't automatically resolve the protocol http silly mistake :)
On Yosemite, I am unable to access multiple pages using Chrome & Safari, but for some reason Firefox always works. But with this, I'm unable to install certain tools using terminal which is the real problem. For instance, python.org is unable to load because Safari can't establish a secure connection (same with chrome). Firefox opens the site just fine, is there any reason behind that?
Update
Not behind a proxy. I'll stick with GitHub.com as an example. It opens perfect on firefox, no problems. With Chrome, it will come up without any styling (css/images), just the plain text. If i open the developer console, there are a bunch of "Failed to load resource: net::ERR_INSECURE_RESPONSE", its all the styling that didn't load. Same with safari, text show but no styling.
When using chrome dev tools to emulate mobile devices, sometimes when toggling emulation from mobile back to desktop the user agent spoofing gets stuck in mobile. I've tried hard cache reset, closing browser completely, restore to default.... but anything I do the site still renders in mobile (even when emulation is turned off).
This happens in Canary, beta, and regular Chrome.
Also a note i've only seen this happen in Sharepoint.
Anyone know how to resolve? Nothing seems to get the dev tools to change user agent back to default when exiting emulation.
Have you tried deleting your chrome settings?
Windows: C:/Users/%username%/AppData/Local/Google/Chrome/User Data
Mac OSX: ~/Library/Application Support/Google/Chrome/
Ubuntu: ~/.config/chromium/
Also make sure you aren't ZOOMED! Gets ya everytime
I ran into this same problem previously when using dev tools in Chrome to look at mobile resolutions that got me permanently stuck in mobile for SharePoint only. I solved it originally with the recommendation above of deleting my Chrome settings folder, however, that meant I had to sign in again, sync my extensions, etc.
After forgetting that this would happen again, I ran into the same issue, but this time I discovered that if you append the following to your SharePoint URL it will reset this back to non-mobile. I verified that it is not temporary as I have closed my browser, reopened, visited SharePoint, and it still loads in desktop mode.
/?mobile=0
So, you would use your site url, e.g. https://siteurl/?mobile=0
Weird, this just started happening to me. It persists in new tabs and new windows. Only fix is to open DevTools and switch to Responsive mode and then pull it way out. As soon as I turn off Responsive / Mobile view, Chrome snaps right back to a mobile view by default (appears to be iPad size).
The solution for me (so far) was to quit Chrome and open it back up.
I am trying to automate mobile web site, so i am using virtual browser in Testcomplete 10. But i couldnot able to map any child object from parent.
I can take main page screenshot only. Below steps i had done,
1) opend www.google.com by using virtual browser with Apple ipad or any other
2) took screenshot for main page, Name Mapping path : Aliases.browser.BrowserWindow.Chrome_RenderWidgetHostHWND
3) Trying to map Google search textbox, but could not map that child objects from parent("Chrome_RenderWidgetHostHWND").
Can any one confirm possible solution for this?
I guess you're using Chrome 34?
You need TestComplete 10.10 with the Chrome 33 patch (it works for Chrome 34, too).
Also, make sure that the TestComplete extension version in chrome://extensions is 10.10.xxx; otherwise uninstall and reinstall both Chrome and TestComplete as explained here.
I'm currently trying to set up a connection between my web client and my iOS app, but for some reason my iOS client only sees a black box when using Chrome (version 33). I can see the video just fine if I use Firefox (both in my app and when I put the browsers side-by-side, they can see each other).
This doesn't appear to be a documented known issue with the JavaScript SDK, and I can't see any recent discussion about this on the forums (last post was mine).
The iOS sample can be located here (samples/OpenTokHelloWorld) with the browser page in samples/OpenTokHelloWorld/browser_demo.html
I suggest cd'ing into samples/OpenTokHelloWorld and running python -m SimpleHTTPServer, as it can't be run from a file:/// path.
Here is what my iPad sees:
Chrome:
Firefox:
And Chrome/Firefox (respectively), both publishing video from the same camera
Edit: after testing on other machines, it may be something specific to my environment even though none of my extensions run in Incognito and I don't have any custom plugins installed.
It looks like the OpenTok mobile SDKs with the specific webcam I was using has issues. On Android the video stream will display for a brief moment then segfault, and on iOS there will be no video at all.
I have tested this many times and could not reproduce what you are seeing in your chrome.
Without seeing any console errors or iOS logs the best suggestion is to try clearing your cache, or maybe restarting your computer (longshot)