In the past few days I have been developing a unniversity project on Visual Studio by debugging on Google Chrome every single time.
Now I suspect that after updating my Windows 10 to the latest version - 1803 - something has stopped working while debugging on Chrome. The menus are no longer responsive, if I try to resize my page the content doesn't seem to go to the placed they used too and the text style has changed aswell.
NOTE: Debugging on Microsoft Edge appears to be working as expected.
Creating a new project with a bootstrap theme and debugging on Chrome gives the very same issue. Is there anything I can do to solve it?
Here's some screenshots of it debugging on Chrome and Edge.
Related
For some reason, my OSX Visual Studio Code has stopped indexing CSS files.
Neither Outline nor Go to the symbol are available.
I tested and symbol and outline information still comes correctly from JS files, but not CSS. I also tested creating a new workspace and the problem persists.
How can I diagnose language service issues in Visual Studio Code and fix the problem? As far as I know, the support for CSS file indexing worked with Visual Studio Code out of the box.
You can open a developer tools from Help > Toggle Developer Tool. It shows VS Code internal JavaScript errors and debug output.
This line gave a hint:
PostCSS Language Support extension was loaded and it broke language support for normal CSS, or stopped indexing CSS symbols. After uninstalling PostCSS support CSS symbols started to work again.
When I run the application with Visual Studio and ripple, and I click link for other pages from Cordova project( to localhost) comes an error. Ripple notificates: "Instead of the page you'll see an AW, snap!" Chromes DeveloperTools tells: "was disconnected from the page.'
Links for some website works good. Before links worked well.
What could be the problem?
We found what appears to be a bug in Chromium and filed this to track it:
https://code.google.com/p/chromium/issues/detail?id=585260
We are making a change to Ripple to work around the issue. Please keep an eye on our VS TACO blog for more information; we'll make an announcement when the change goes live with instructions on how to update Ripple. You can find our blog here:
http://microsoft.github.io/vstacoblog/
We're sorry for any inconvenience this has caused you and hope to have a fix, both in our tools and in Chrome, shortly.
(Disclosure: I work on the Tools for Apache Cordova in Visual Studio)
I followed instructions from http://microsoft.github.io/vstacoblog/2016/02/12/update-to-ripple.html
and it's working :
-In Visual Studio, click Tools -> Options
-Find the Tools for Apache Cordova
-Click the “Clear Cordova Cache” button
-Rebuild your project
Please make sure that you have VS2015 TACO tools update 5. let me know if you have any issues afterwards. It works great for me with the latest update.
Luck did not last a long time. Chrome updated himself(Versio 48.0.2564.103 m) and Ripple does not again working. In new Chromes is bug with Visual Studio 2015 and Ripple.
This is a new issue we're investigating on the VS TACO team, too. I'll update this answer with any workarounds/next steps as we keep researching.
For now, the workaround is as suggested by #PeteQoo - you need to revert your version of Chrome to version 46.
I have one interesting issue on this project, which is actively using Visual Composer WP Plugin.
When one of my clients tries to view the site on
MacBook Air OS X El Capitan
Safari v. 9.0.1 (11601.2.7.2)
the browser does not show any images on the main page. They are all loaded to the DOM and can be saved and then opened like a separate file, but on the web page it is just an empty space (smth like css {opacity: 0} rule).
I've been looking for some articles on this issue, but most of them refer to official forums and browser settings fixes. But it is not the case, as this client has a complete user experience on other web pages. And I must say it'is working fine on all the other major desktop and mobile browsers.
Update
Tested with
Safari 8.0.4 (10600.4.10.7)
MacBook Pro OS X Yosemite
works like a charm
I have an application that is using GWT 2.0.4 and running fine on IE8 browser. When opened in IE11, it is giving blank page with error message given below.
com.google.gwt.core.client.JavaScriptException : (TypeError) : Object doesn’t support property or method ‘attachEvent’
The exception was thrown because “attachEvent” is a deprecated function used in older versions of Internet Explorer. IE11 uses “addEventListener” method instead of “attachEvent”.
The user.agent value was set to "ie6" so i changed it to "gecko1_8". After changing user agent it opens the application but the data in table(GWT-ext GridPanel) is getting overlapped over one another, scrollbars are missing and the alignment of menu bar is changed.
It is working fine after enabling the compatibility mode. What is the proper workaround to run my app in IE11 ? Do i need to upgrade GWT and if yes then to which version supports IE11? I don't have to use "X-UA-Compatible=IE8" meta tag....Please help
As with anything on the Web, you should always try to run the latest version, because everything changes around your application. 2.0.4 is 5 years old already!
So yes, upgrade to the latest version of GWT (2.7.0 as of today), and when the next version will come (2.8, in a few weeks) try to upgrade as well.
As a workaround, because it works in IE8, you could probably ask IE11 to emulate it using an X-UA-Compatible with value IE=EmulateIE8. But that's only a temporary workaround, as the next version (Edge, coming in Windows 10 to replace IE) will no longer support X-UA-Compatible (except in the Intranet zone). See the warning at the top of the X-UA-Compatible doc and this announcement by Mirosoft. The real solution is to stay up-to-date with GWT versions, just like you stay up-to-date with browser versions.
I am working with a symfony 2 project. I am in development environment and the symfony debug bar displays well with any browser but IE8. It looks like the css for this bar is not loaded with IE.
After investigation, the problem occurs after the 2.0 version (so for 2.1 and 2.2)... maybe web debug bar css is CSS3, it would be quite an error to do for Sensio Labs.. I dont believe it
This is indeed an issue, a bug of Symfony versions above 2.0 : the web debug toolbar is not displayed properly with IE8.
This issue has been reported, and a solution given
https://github.com/symfony/symfony/issues/7422#issuecomment-15112627