We have an internal Windows server with OpenFire 4.5.1 with inVerse 6.0.1 Release 1 installed. The plugin works great from Chrome browser and Edge browser, but I really need it to also work from IE11, if possible. When initial page loads, there are 2 errors:
IE11 console image
If you can't see the image: 1. Syntax error converse.min.js (55,35487) 2. 'converse' is undefined inverse (43,17).
Looks like a show-stopper. Not sure how or if a fix is available.
Thanks!
From the Converse Github issue, we can see that there have many threads about Converse plugin not support IE browser. Such as: Support for IE 11 and iOS Safari 9.3
According to these issues, we can know that Converse uses quite a few features not supported by IE11, not just arrow functions. So, perhaps this plugin doesn't support IE browser or it needs to install some Polyfill. You could contact Converse developer team and ask them whether there have a workaround, or feedback this issue to Converse Issue forum.
Related
When I try to debug it shows this dialog:
Error dialog
And when I clock "fix" It shows this:
Web Browsers dialog
I can't solve this problem, any suggestion? Also I am developing a react native app. But i don't think that's the problem...
I am running Intellij Idea in Elementary OS.
This is expected - debugging is only supported in Chrome and browsers of the Chrome family, as it's clearly stated in Help. So, when you start the debugger, the IDE will try to open Chrome regardless of the browser chosen in run configuration. You need to make sure that Chrome is installed and the correct path to it is specified in Settings | Tools | Web Browsers.
We used to support Firefox Remote Debugging (but without source maps) through the FireFox Remote run configuration, but our solution doesn't work in the latest Firefox versions due to changes in the protocol, and there doesn't seem to be an easy way to fix it. We've made some progress recently, but there are still some blocking issues
related ticket: WEB-45986
I'm debugging a React Native 0.61.5 app with Chrome and usually when code stop running on a breakpoint and I hover a property, I can see all the details of it in a popup window. But for two days now I can't get back this functionality. I restarted computer, cleaned Chrome and Metro bundler, tried with virtual or real device but it's still not working. Did I deactivated something accidentally ?
Update:
The issue seems to be resolved with the new Chrome update 79.0.3945.117.
Yes, with Chrome 79 this functionality was broken. This is the thread where people are reporting this bug:
https://support.google.com/chrome/thread/22882968?hl=en
(and also in the link from the comment to this question)
And this is a thread where Chrome developers are tracking this issue and trying to fix it:
https://bugs.chromium.org/p/chromium/issues/detail?id=1033022
In Chrome Canary (81) this feature is working, and it's reportedly working in the Chrome Dev version (80). Other alternatives are Firefox (also people say that it's working in Opera and other browsers) and debugging via VSCode.
It seems they aren't going to fix it until the version 80, which isn't expected to be released until February (from what people say in that thread: https://support.google.com/chrome/thread/22882968?hl=en).
Also there was this change: https://chromium-review.googlesource.com/c/chromium/src/%2B/1835357
which made variables appear on hover only inside the innermost scope. Update: this feature (to evaluate outside the innermost scope) will probably be restored:
(from https://bugs.chromium.org/p/chromium/issues/detail?id=1033022)
"This undoes
http://chromium-review.googlesource.com/c/chromium/src/+/1835357,
which limited the eager popover evaluation to the innermost scope, which
is the only scope for which we can produce reliable results right now.
For the outer scopes, it might still produce the right results, but we
can't guarantee that. But the feature is still very useful and so we are
restoring the behavior here, and will follow up with a proper fix and UX
later".
Even with last Google Chrome update I was not able to resolve this issue. The issue comes from the Chromium version of Google Chrome.
You need the version 81 of Chromium who fixes the bug.
I downloaded the last Chromium browser with Chromium 81 and it's working for me https://chromium.woolyss.com/download/fr/
Using either 20.0.1387.82 or 22.0.1457.0 (developer)
When I right-click and select Inspect Element, I get a vanilla Developer Tools dialogue:
not the one always pictured:
It looks identical to Chrome's debugger (though I've uninstalled Chrome), most notably absent, the icons on top row and the remote debug facility.
Anyone know how I can get Dragonfly working on my machine?
Opera ditched their Presto rendering engine and built a new browser (also called Opera) around Blink (Google's fork of Webkit). It doesn't support Dragonfly any more.
There are plans to port it to the new browser.
Anyone that has installed the new IE9 know if I can keep IE8 installed? I do a lot of web testing and don't want to update to IE9 if I loose IE8.
best way is to install a Virtual Machine
Per Microsoft:
If you are running Windows Vista or
Windows 7 on your computer, you can
install the Internet Explorer 9 Beta
to replace your existing version of
Internet Explorer. After you install
Internet Explorer 9, you can uninstall
it to restore the previously installed
version of Internet Explorer.
So no, it will overwrite IE8 (at least the Beta will. I suppose this is not guaranteed to be the same for the release version).
I use Virtual PC with images of the browsers I need to test, but also and more lately, IETester, http://www.my-debugbar.com/wiki/IETester/HomePage. It allows you to run multiple versions of IE side by side.
If you want to be able to play with the new features of IE9 without installing the entire browser (which will replace IE8) you can install the Platform Preview. The PP is stand-alone, includes the latest features and bug fixes and has been getting updated roughly every 8 weeks. You can get the latest Platform Preview at:
www.ietestdrive.com
FYI: the production IE 9 does not accurately reproduce IE 8. I've got a CSS issue I'm chasing down now because IE 9's IE 8 mode isn't the same as real IE 8.
If you are concerned with testing how your site looks in IE8/7, you can use the Developer Tools (press F12) to switch the Browser modes and Document modes so that IE9 interacts with the web server as a different user agent, and renders the HTML document according to the version rules.
http://msdn.microsoft.com/en-sg/ie/ff468705(en-us).aspx#_New_Dev_Tools
IE9 beta is released as a Windows update, so after installing it and playing around, you can remove it from Programs and Features -> Installed Updates, which will recover IE8.
hit f12 on ie9, it will pop up the debug console. In the menu there is a browser mode option where you can set the browser to display as ie8 and a bunch of other versions too.
Also, if you're mouse focus is on the console and you hit ctrl+r, it will clear your browser cache... This is a feature that all the other browser debuggers lack.. ability to quickly clear cache.... I'm rambling now.
The best way to see your site on old versions of IE is that:
If you have IE9+, open your current version of InternetExplorer, press F12, click on "Browser Mode" tab, then choose the version you want.
see screenshot here:
Works better than IE-tester, and easier than using virtual machine.
I've just read about the release of Safari4 (beta) and its much improved Javascript engine.
I was planning to start playing with it, but I am wondering if anybody knows if both Safary 3 and Safari 4 can be run side by side.
You could run Safari 3 and use the nightly builds of Webkit to test the new engine. You'd be still missing the new features like Cover Flow and Top Sites though.
Try this
Safari normally use the Web Kit
framework found inside Mac OS X to
render web pages and execute
javascript. This means that if you
preserve an old version of Safari to
run it on a newer version of Mac OS,
it will use the newer Web Kit found in
the system and you will get the same
results as with the newer version.
However, the link has some stand alone versions that you can install.
There's also this which shows how to create your own stand alone version.
Beatnik Pad has a quick tutorial that shows how running Safari 4 Beta and Safari 3 side by side can be accomplished.