It looks like a WebSocket creation problem, which should not be happening with chrome.
I tested it with different browsers (including chrome) from different machines (same OS same NW config) and it was OK.
How is this even possible?
I was struggling with a similar issue with chrome and safari about 3 years ago.
In my case it was, at the end, an issue of WebSockets versions
Basically there were 2 main protocols of WebSockets: Hixi and Hybi, Hybi becoming the successor
You mentioned that with the same config one chrome browser works and one gives you that error. Can you please check the versions of Chrome on both scenarios?
I know its a long shot, but if the "broken" one is running a very old version, say bellow 14 from around 2011, according to the chrome version history - this just might be it
BTW, which server are you using?
Related
history.go(-1) has no effect in iFrame from different domain, but works in chrome on another machine.
Given a start page with an iFrame from a different domain.
And a FirstIFramedPage.html with a link to SecondIFramedPage in the different domain.
When I click on a back button with onClick="window.history.go(-1)" it has no effect.
However, it does have the desired affect (to navigate the frame back to FirstIFramedPage.html) in every other browser I've tested AND on another machine with the same version of Chrome.
chrome: Version 66.0.3359.181 (Official Build) (64-bit)
I have a fully working example here: https://github.com/jimlesch/ChromeIFrameHistoryFail
the readme.txt has instructions on how to reproduce this issue.
What I've tried:
running in incognito mode.
disabling extensions.
using an iframe from the same domain (works as expected, but not possible in my scenario)
Uninstalling and reinstalling Chrome.
Installing Chrome Beta to see if it behaved differently (still fails for me on 5)
Looking at chrome://tracing (could not make heads or tails of it)
I am looking for help on how to further isolate this issue, since I cannot reproduce it on another windows 10 machine with the same version of chrome. Thanks for any help you could provide.
It would appear this is a chrome bug introduced in field trials of "Site isolation". These field trials get applied to 10% of the stable build (and 90% in beta builds).
I was able to revert to expected behavior by choosing to "opt out" in "Site isolation trial opt-out". This setting is available under: chrome://flags/#enable-site-per-process.
Also see this duplicate bug for a richer discussion: bugs.chromium.org/p/chromium/issues/detail?id=845923
As my application only support Chrome browser and try to test it using IBM RFT.
Issues:
Browser enablement test is fail while testing Chrome from Enable Environment in RFT
Due to that not able to capture any objects in Chrome using RFT
Tried the below steps as well but not able to resolve :
https://www.ibm.com/developerworks/community/forums/html/topic?id=1e5ec381-03c3-4ab6-a9b8-4ce98f592b3b
If anyone face the same issue previously please do reply.
If you are using Chrome 45(Where NPAPI is disabled ) or above , you need to install RFT 8.6.0.5 on top of which a test fix is available that will allow you to execute/playback your existing scripts. To get the testfix you will need to contact the product technical support.
Rational Functional Tester old versions doesn't work with Chrome anymore. In their last release notes (fix pack 4) the greatest "feature" is to make it work with newer versions of Chrome. I have the version just before this one and I guarantee that it doesn't work with Chrome. The update process is really error prone. Reserve at least day to do it.
We had to update our certificate for our ecommerce website recently and ever since we've noticed weird behavior in Firefox and other browsers. About half the computers in the office, as well as my home computer complain that the certificate chain is not complete (Very odd it's not universal). I can view the chain in the Firefox certificate viewer and see that it doesn't have a chain.
Meanwhile Chrome's chain looks fine. This leads me to believe that there isn't an issue with our install of the certificate, as there's a chain there to be read, but Firefox can't seem to see it.
I should note that it seems to have the same issue in Chrome on Android.
So is this our problem or Firefox's?
This is typically the case when the server does not send all necessary intermediate certificates. Chrome on Desktop will go and fetch them. Firefox will use any intermediate certificates cached from previous connections to other sites but will not fetch missing certificates, thus some Firefox instances might work while others not. Chrome on Android will also not fetch missing certificates.
The issue needs to be fixed on the server side. If you check the server at SSLLabs you will probably see a note regarding "chain issues". Add the necessary certificates (they are listed at the report) until you don't see this note any longer and then it should work with the other browsers too.
Chrome (on Win and Linux) was unable to load https://apscatalog.com.
Though all other browsers and Chrome on Mac was able to load site with no warnings or errors.
Even external tools say that everything is fine: https://www.ssllabs.com/ssltest/analyze.html?d=apscatalog.com
How can I fix this issue?
Update
It seems to be a Chrome bug. Chrome v.33 works fine while v.32 fails
I would say, that the they have some broken appliance (firewall, load balancer...) in front of it. From wireshark I see the Client Hello from Chrome, but it never gets a response, not even an ACK that the packet was received. That's why it's retransmitting the Client Hello again and again until it finally gives up. I've seen such problems with older F5 BIG-IP load balancers (it's fixed in the meantime, but there are still some broken ones out there) but this does not seem to be the case here. So it's probably yet another broken appliance :(
In case you have knowledge of the infrastructure there I would really like to know what device this might be.
Interesting that https://apscatalog.com works if chrome is started with ssl-version-max=tls1:
google-chrome --ssl-version-max=tls1
With IE 10 testing my website on older versions of IE was very easy and always worked as it should, I just went to the developer tools, picked the version I wanted from the menu and I had no problems.
Now, after upgrading to IE 11 I encountered some problems with this method of testing. First, stuff I put inside HTML comments like <!--[if lt IE 10]> don't show anymore. Second, the same website that I tested a few days ago on older versions of IE with IE 10 looks very different when doing the same tests on IE 11.
So, why do all this stuff happen and how can I solve it?
Internet Explorer 11 shipped with a fairly good set of emulation tools. If you know what issues are being reported in Internet Explorer 10, you can attemp to replicate those in emulation. If you succeed, it's very likely that you can proceed to troubleshoot those issues while in emulation.
At times you may run into some things that aren't reproducible in emulation, and instead require a native instance of Internet Explorer 10 (or any other version for that matter). At this point you really only have a couple of options:
Virtual Machine in your browser (http://browserstack.com)
Virtual Machine on your desktop (http://modern.ie)
Each option has its own set of pros and cons. In-browser virtual machines can be spun up very quickly, and don't require a serious amount of system resources to run. That being said, the experience can be choppy and not conducive to troubleshooting issues that rely on low latency.
Desktop emulation is great because you have a more near-native feel. Unfortunately, this means you need to download very large files to get a second operating system running within your current operating system. Furthermore, you may find yourself wrestling with configurations and more.
I personally use a combination of the two, depending on what issue I am presently trying to troubleshoot. As a good practice though, writing clear and valid markup, along with using best practices like progressive-enhancement, and feature-detection to serve up alternate code-paths, results in a lower chance you'll have to spend much time debugging anything.
The latest ie11 have functionality of like previous ie browser version.
1 To access the modes, start the F12 Developer Tools,
2 click the Emulation icon at the bottom, and choose a Document Mode — they’re not named “browser modes” any longer
This article may help you.
http://www.sitepoint.com/ie11-browser-modes-return/
I had users complaining about issues in IE10, and was not able to recreate them in IE11 using F12 emulation. What I ended up doing (after many attempts to uninstall IE11, and install IE10 to no avail (in Windows 10)) was this:
Download VirtualBox here: https://www.virtualbox.org/wiki/Downloads
Go to: https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/
Download the VM you want to test with and then load it into VirtualBox. There are instructions on their website on setting options etc. Mostly you need to set memory, and virtual hard disk location and size. I used 1024MB and the default for the drive, since I am only running IE with this VM. It worked great. Networking by default put the host at 10.0.2.2 so my localhost test website running on localhost:8080 was at http://10.0.2.2:8080// on the VM. It worked well.
Hope this may save someone some time.
The emulation missed two different bugs one with Array.filter, and another with __definegetter__.
The VM picked these up. It is a slower approach than emulation.
Just saw the "On IE11." Sorry about that - still this is my recommendation. And you don't have to uninstall IE11.