I am looking for a way to hide some folders or files, for example in the chrome inspect tool (F12) under the sources tab.
I am developing a web application with angularjs and i want to hide the app folder that contain some js files with sensible data.
Related
Chrome dev tools sources tab does not show all css/js files. The css/js files are in the head section, and can be loaded successfully from another tab using their URLs. Could not debug source now.
I'm trying to build a Chrome extension A that makes use of network requests -- however, the network requests that are relevant to me are made through a separate extension B. Meaning, the network requests aren't viewable on the main 'inspect element' panel but only through inspecting extension B's background page in developer mode.
Is there any known way to access this information through extension A?
Thanks.
When using the Microsoft Edge browser, by default when you open a PDF it will open the PDF in a new tab using the built-in PDF viewer. To avoid this, you can adjust the browser's settings: Toggle on the "Always open PDF files externally" option. This works great. However, it presents a separate issue. Our internal applications use embedded PDFs in iframes. When the external toggle is set to on, these PDFs will not show in the iframes. This doesn't happen in Chrome. Has anyone else experienced this and know a work around?
I've tried removing the type="application/pdf" from the iframe tag to no avail. I can't find anything else online.
It looks like an expected result because you have enabled the option Always open PDF files externally.
So MS Edge browser is giving you an option to download the PDF file and open it using the desired app.
You said this doesn't happen in Chrome browser.
If you enabled the Download PDF files instead of automatically opening them in Chrome option then you will notice the same result in the Chrome browser.
Output in the Chrome browser:
If you click on the Open button then it will download the PDF file.
I did not get any solution or a workaround for this issue.
If you think that there should be an option to load the file in an iframe if Always open PDF files externally option is enabled then I suggest you click on the Send Feedback button in the MS Edge browser and try to provide your feedback about it to the Microsoft.
I posted feedback suggesting that an exclusion/inclusion list be in included but the simplest way would be to treat the frame as part of the session. But this is not Microsoft it is the Chrome projects issue.
In the Developer Tools window within the Chrome Browser, there is a "Sources" tab which in the past, I have been able to set breakpoints and step through the Javascript. I am still able to do that for a web app that I wrote. However, when I try to do the same for some another web app, the javascript file does not appear on the Sources tab. Instead, I find it on the Application tab but I do not appear to have the ability to step through the breakpoints on that tab.
How does the Application tab differ from the Sources tab and how might I be able to debug the javascript file?
Chrome Devtools's has some some undesirable behaviours regarding to css sourcemaps like in this link https://code.google.com/p/chromium/issues/detail?id=257778.
Is it possible to edit Devtools's itself (like Style Panel) so I can do things like directing sourcemap links to open them in editor or prevent loss of sourcemaps? I was able to edit Opera's Dragonfly from the local source. Is it possible to make similar changes with Devtools?
You can edit DevTools UI and serve it from local source tree. See this doc for more details.