I am working on a .NET 4.5.1 project in Visual Studio and have Web Essentials installed and functioning in all other ways except finding unused CSS. When I test with a new project, it works as expected.
Is there a known situation in which Unused CSS will not work?
Environment:
VS2013 Pro
Win7 Pro
Steps to reproduce:
Start debugging the app in Chrome
Once the site opens in a new tab, select Start Recording in the Browser Link Dashboard
Change content by clicking through the site
Results:
Recording has started and Stop Recording is now available
There are no messages sent to the output window
Clear CSS Usage Data option in the Browser Link toolbar (in the top menu) is disabled. It never is enabled whether recording or not.
Expected:
Messages in the output view
Ability to clear CSS usage data
Attempts to troubleshoot:
Installed prior version of extension - same result
Verified the issue exists on Chrome, Firefox and IE
Other features of Browser Link work as expected
Creating a new project works as expected and "Clear CSS usage data" is not greyed out
Browser Link drop down menu
I know it's a long time since you asked this, but this solution might actually help someone else...You can identify unused CSS using Chrome Dev tools
Open your chrome Dev tools
Click on the Audits tab
Click on Run at the bottom, wait for the audit to finish
You will get unused CSS under Remove unused CSS rules in the Web Page Performance section
Related
I have created a personal Tabs app and deployed the same on MS teams.
Things are working as expected, but at 1 stage of time, my application goes back to the original "contentUrl" page as defined in the manifest.json file.
This might be an issue with my frontend code, so i wanted to understand how can we debug the frontend developer console to check if there's any error being thrown from my application?
The only way to figure out what is going on is to use the DevTools. To use DevTools in the desktop client, you must:
Ensure you have enabled developer preview.
Open up a tab so you have something to inspect with the DevTools.
Open the DevTools one of the following ways:
On Windows, you open DevTools via the Microsoft Teams icon in the
desktop tray.
The following example shows DevTools open and inspecting a tab configuration dialog:
Ref Doc-https://learn.microsoft.com/en-us/microsoftteams/platform/tabs/how-to/developer-tools
Lately Firefox Storage tab in it's Web Dev tools is not working correctly for me. When there are changes in the localStorage, the data displayed in the tab doesn't update, not even when I refresh the page. For it to work, I have to close Web Dev tools and then reopen it.
I tried using a fresh install of Firefox without addons, tried both Linux and Windows, tried in virtual machine, and still won't work, so I'm guessing it must be due to some recent update.
To reproduce the problem:
Go to any website
Open Web Dev Tools (F12)
Go to Storage tab
Right click Local Storage file and delete all
Refresh page to check if Storage updates
Anyone else having the same problem? Glad if anyone can help.
As I am a web-developer my work reley on web browsers .
I edited html and css files to get the exact result I want in the web design but from very starting chrome loads from its chache memory , You know chromium also do the same thing . It become very difficult for me check each time I have to change the URL in order to reload the web page to check the changes I have made on the page. While on the firefox and edge its all great up to time , please tell me the solution how can I remove this setting of loading from chache in chrome ,
I use windows 7 and 10 on my laptop
currently using chrome -Version 57.0.2987.133
You can disable chrome caching :
check out this :
Disabling Chrome cache for website development
or you can install Clear Cash extension from google chrome extensions
The Chrome DevTools can disable the cache.
F12 or Right-click and Inspect Element to open the DevTools. Now click Network in the toolbar. Finally, check the Disable cache checkbox at the top.
I'm developing an application - something I've done on the same machine for the last x years.
I'm still using XP on this machine - VS 2010. I've also recently changed from the default dev host to IIS 7.5.
At them moment, I'm checking out Google Polymer - this is where the root of my problem lies. When I click on a trivial link to open a dropdown menu, the CPU goes into overdrive and stays there. This only happens on Chrome, not Firefox.
I eliminated a rogue polymer installation by linking direct to the polymer site url's.
I paired the page down so its just html - no aspx.
I put the page up on codepen and I do not get the same issue.
I removed all extensions from Chrome and reset my settings.
I switched betwen IIS and the default dev host.
After these tests, the only variant is that copepen runs the page and I run the page. Therefore my conclusion is that it must be something to do with VS or IIS/dev host.
I'm scratching my head as to where to go next with this. Has anyone else had similar experiences when testing on Chrome?
Help!
Confirmed here : VS 2013 (32bit) + Google Chrome = 100% CPU Windows 8 & 10
You need to diable BrowserLink option in the VS 2013
here is how you can disable it
http://www.asp.net/visual-studio/overview/2013/using-browser-link#disabling
After liasing with the guys from polymer project for sometime, I decided that polymer wasn't ready for production just yet.
I recently downgraded IE from 11 to 8 due to IE 11 not having the ability to run as previous versions. After the downgrade, I suddenly was not able to debug a web app from Visual Studio 2010. While using IE 11, I was still able to hit breakpoints in the JavaScript code but now, none of my breakpoints are hit and instead when I navigate to the page where I think the error is, I get a pop up window titled Webpage Error with a message of "Do you want to debug this webpage? This webpage contains errors that might prevent it from displaying or working correctly. If you are not testing this webpage, click No." I've never seen this pop up appear while using IE 11 or the IE version before I upgraded to IE 11.
Is there an IIS setting that gets overridden by downgrading? I'm using IIS 7.5. How can I get back to seeing my breakpoints getting hit in VS2010?
Update:
In VS 2010, while in debugging mode, I clicked Debug > Attach to Process and noticed two processes for iexplorer.exe. On that is grayed out (which I'm assuming there is a debugger attached to) but has no title. And the other has a title that matches what I see in the actual IE window. Back in IE, when I see the error popup asking me if I want to debug this web page and I click yes, I get a new popup with the title of Visual Studio Just-In-Time Debugger with the message that includes "An unhandled exception .... occured in iexplorer.exe[4508]. This process ID matches that of the grayed out iexplorer process. Why would there be two iexplorer processes?
I have VS 2012 installed as well but not sure if that changes anything.
Thanks,
Going all the way back to IE8 is overkill-- use IE10 instead. The IE team removed the "emulation" features from the pre-release IE11 developer tools because the emulations were never very accurate; you should instead use VMs instead (see http://modern.ie)
All versions of IE since IE8 use two or more processes: One process is the Manager/Frame process and one or more processes represent the tab/content processes where your HTML and script run. You want your debugger to attach to the tab/content process, which is a child of the manager/frame process.
The "Do you want to debug" prompt is controlled by Tools > Internet Options > Advanced; see the 2 "Script debugger" checkboxes near the top of the list.