After a window 7 update, live chat won't open from any browser.
Script works fine from other laptops and browser, but not from those with win7. The links open the livechatinc.com page, and in console I get:
LC_Invite is not defined
I went through some forums and found this maybe your the problem is that LC_Invite is still being loaded when onChatLoaded is called.
Related
We have a Wordpress based website (rendeljkinait.hu), and we face freezing issues while editing articles when using Chrome. When I hit the save button for the 7th time without page reload, the article editor freezes during save and I get "waiting for available socket" error in Chrome. No matter how long I wait, the editor won't save until I reload the page. When I'm using Firefox, everything is fine, no matter how much I hit the save button. Current Wordpress version is 5.2.3, but error occured in former versions too.
I investigated the error, and found it is caused because Chrome never closes the open sockets until I reload the page. So until hitting the button 6 times everything is fine, since Chrome and other modern browsers allow to have maximum 6 paralell connection to a single host. But after I press the button for the 7th time, there is no space for another connection, so Chrome is waiting for the older connections to get closed, but it never happens.
Here's a screenshot from net log
Using Firefox I observed that it always closes the connection after the save is successful, so only 1 connection is active all the time, it never exceeds the 6 paralell connection limit. I attached Chrome netlog file here, you can view it here. I also attached a video showing Firefox closing the connection here (107.6.*.** is our servers IP).
For various reasons we have to use Chrome, so I would like to find a solution for this problem, but I'm completely stuck. Does anyone have a suggestion what could cause the problem and how to solve it?
Thanks in advance!
I have the same problems with chrome and gutenberg.
It is impossible to do any heavy editing on the site, so I use firefox for all admin related stuff.
Haven't found a solution either...
For anyone who might find this topic with similar problem: seems like it was a Wordpress bug, a Wordpress update solved the issue.
We have an Application Developed in ASP.NET inside which we have added an embedded Power Bi Dashboard using iFrame.
The Dashboard is working as expected in Chrome but facing the following issues with IE and Edge.
On IE the Dashboard is not being Displayed when viewed from the Embedded Application and upon clicking the power bi Sign-In button (shown within the Iframe), the application as a whole gets redirected to app.Powerbi.com/.... When you click the back button and refresh, still the sign-in prompt is shown in the iframe.
On Edge, the behavior is same as in IE, except that you click the back button from the app.powerbi.com website and then refresh the page, then the report renders correctly within the Iframe.
I tried clearing the Cache and Cookies, tried adding *.microsoft.com site and *app.powerbi.com to trusted sites list(per power bi forums) but still not working.
I suggest you check for the latest Windows updates and try to install it. Then after again try to test this issue on your side.
If the issue persists then hard refresh the page. Clear all the data for that site and again try to load the page.
I tested the issue with IE 11.1.18362.0 and Microsoft Edge 44.18362.1.0. As per my testing results, both browsers display the Power BI dashboard in ASP.NET site without any issue.
Output in IE 11:
Output in MS Edge:
If the issue persists then try to check the console to see whether there is any error or warning message. It can help to narrow down the issue.
I'm using the latest Meteor + latest React. A couple of days ago it stopped auto-refreshing on file change in Chrome. I opened Safari and it worked there, so I continued my development using it. Today Safari stopped auto-refreshing as well. There are no errors in any of the consoles (meteor or browser). I do get Client modified -- refreshing (x12) messages in Meteor console, but nothing else happens. I removed the .meteor/local/build folder and restarted Meteor but that didn't help. Looking for any pointers to fix this. Thank you in advance
Update:
It does work when in incognito or in regular browser window but only if I'm not logged in to the site. Once I log in, there are three local storage items created: Meteor.userId, Meteor.loginToken, and Meteor.loginTokenExpires. And auto-refresh no longer works. If I log out, auto-refresh starts working again.
I have a bit of a brain teaser. I am getting the attached server error when I load ANY page on my website. However, this ONLY happens in Firefox. Any other browser loads the page just fine. I have cleared my cache and have completely uninstalled and re-installed FireFox to no avail. Any idea why a server error would only show up in certain browsers? This is a windows based machine running IIS. I'm totally stumped. Thanks!
It's hard to see the exception type because the text is so small on you resized image.
Have you tried monitoring the request using Fiddler, or launching FF Dev tools (CTRL+SHIFT+I from FireFox)? Is there anything in that output that could reveal a clue?
Is there a way to get MonoDevelop to not open a Safari (or other browser) window when I debug a web site? I still want it to fire up the XSP web server, and kick into debugging mode.
Reason being because I'm hitting the server code being debugged from another location, and I don't want to have to keep closing useless browser windows over and over.
A bit of a hack, but I'm now just calling window.close immediately after the page loads from JavaScript.
I'm on Linux, and I'm not sure if it will work for Mac, but this is the only relevant thing I found by searching for the same problem on Linux, so this answer is relevant to someone.
I go to the choice of browser (in the build options near the build button) and choose to open it in Vim. For some reason it doesn't want to open in Vim, even though it opens in LibreOffice and in Atom editor just fine. Ergo, it doesn't open anything. So A) this allows page refreshes on the home page. B) There's no opening and closing. C) You don't change any code to modify functionality of an editor.