I'm experiencing a very strange behaviour with Bootstrap 3 when viewing in Internet Explorer. My nav bar works perfectly locally (I'm using VS2012, so the page is being served by IIS Express), but when I deploy it to one of our internal servers (running full IIS) it always appears collapsed (even if I stretch the browser across both my monitors!)
If I user Chrome, it works perfectly.
I've compared the files that are downloaded in each case, and they are identical. I have even create a test file which uses the example nav bar from the bootstrap website, and I see the same behaviour.
So, to summarize:
Local / IE Works
Local / Chrome Works
Remote / IE Does not work
Remote / Chrome Works
Any pointers about this very strange behaviour would be very much appreciated!
I found the problem, and it is Internet Explorer's compatibility settings.
Under Tools > Compatibility View Settings dialog there is a checkbox which says "Display intranet sites in Compatibility View".
This setting meant IE used an older rendering engine, which did not work very well with Bootstrap. Once it was turned off everything was fine.
Related
When debugging my ASP .NET Core Web API application in Visual Studio 2022, I have the Docker configuration set to launch a browser:
This browser defaults to Edge. Is there a way to change this, to Firefox for example? That is my browser of choice and I would prefer it to simply open a new tab in an existing instance of that rather than an entirely separate Edge window.
Firefox is set as my default browser.
Thanks.
You can choose a default browser to use with the docker profile but it's not clear how to modify the list of possible browsers or if you can modify the launch settings for those browsers... anyway, from the debug toolbar menu you'll see the very small drop down menu arrow. Clicking on that gives you a series of drop down menus that lets you choose a browser.
Note the "Browse With..." does not work for me. The project rebuilds and nothing happens when I click that. And "Select Web Browsers..." gives a limited choice of chrome, edge, IE.
Turns out it does seem to use the default browser.
This is a new install of Win 11, and I had installed Firefox within the same session as my attempted debugging with it - a reboot seemed to result in VS using it as expected.
The default browser behaviour is documented here.
i run into a (at least for me) strange issue with vue.
I created an SPA without any remote content. Just a .html file, some css and vue to "jump" between content divs.
The SPA was created for mobile devices.
When i visit the page with internet connection everything works fine.
Now is "add the page to homescreen".
When i open the "app" (homescreen page) without internet connection the click event does no longer work.
When i open the "app" with internet connection, again everything does work as expected.
Does anyone have a clue what's wrong in here?
UPDATE:
The issue seems to appear only on tablet. I have tried on a smartphone and the app does work even in offline Mode.
Maybe relevant:
Tablet: Nexus 7
OS: Android 6.0.1
Browser: Chrome 75.0.3770.67
SOLVED
The issue was, that the JS Code was not stored when adding the Page to the Homescreen. I have added a service worker to cache the assets. Now everything works like a charme :)
I have a JSF application that uses Primefaces 7.0. Some of its pages use the p:media component to display the content of PDF files. When installed on a remote linux server, the application does not show the content of the PDF if used with Firefox 67.0. It works fine with Chrome and IE. And it works perfectly on my Windows 10 PC, even with Firefox. To make it even wierder, inspecting the element makes it visible in my laptop, but not in my desktop computer. Has anyone else a similar problem? Please advice.
EDIT 11/11/2019: Today I learned that the problem occurs when using https instead of http. Therefore, it doesn't really matter that the server is remote; what happens is that on our remote (and public) server we use https
When using chrome dev tools to emulate mobile devices, sometimes when toggling emulation from mobile back to desktop the user agent spoofing gets stuck in mobile. I've tried hard cache reset, closing browser completely, restore to default.... but anything I do the site still renders in mobile (even when emulation is turned off).
This happens in Canary, beta, and regular Chrome.
Also a note i've only seen this happen in Sharepoint.
Anyone know how to resolve? Nothing seems to get the dev tools to change user agent back to default when exiting emulation.
Have you tried deleting your chrome settings?
Windows: C:/Users/%username%/AppData/Local/Google/Chrome/User Data
Mac OSX: ~/Library/Application Support/Google/Chrome/
Ubuntu: ~/.config/chromium/
Also make sure you aren't ZOOMED! Gets ya everytime
I ran into this same problem previously when using dev tools in Chrome to look at mobile resolutions that got me permanently stuck in mobile for SharePoint only. I solved it originally with the recommendation above of deleting my Chrome settings folder, however, that meant I had to sign in again, sync my extensions, etc.
After forgetting that this would happen again, I ran into the same issue, but this time I discovered that if you append the following to your SharePoint URL it will reset this back to non-mobile. I verified that it is not temporary as I have closed my browser, reopened, visited SharePoint, and it still loads in desktop mode.
/?mobile=0
So, you would use your site url, e.g. https://siteurl/?mobile=0
Weird, this just started happening to me. It persists in new tabs and new windows. Only fix is to open DevTools and switch to Responsive mode and then pull it way out. As soon as I turn off Responsive / Mobile view, Chrome snaps right back to a mobile view by default (appears to be iPad size).
The solution for me (so far) was to quit Chrome and open it back up.
I wrote an application using the HTML5 Cache Manifest and I'm having a problem using it in IE 10.
I used Fiddler to witness the manifest file being downloaded and all resources fetched on the initial load of the application. If I disable my network adapter to force the machine offline, the application continues to work as expected as long as I don't close the browser window.
However, when I close the browser window, then attempt to re-open the page from a favorite, IE 10 tells me "You're not connected to a network". Obviously I know that, I'm trying to use the app offline. These exact steps work in Chrome.
Is this behavior by design? Is there a workaround? I can't test with IE 11 right now...is this different in IE 11?
Hearing of some issues of the appcache clearing if your company utilizes gpo settings and has "empty temporary internet files folder when browser is closed" enabled.
Did you find the answer to this? I have the same problem. I did get a bit further though. I found that if you go to the IE10 File menu option and tick Work Offline then try and access your cached app it loads the page but I still have an issue as it does not appear to be using the javascript file that should also be cached. All works ok on Google Chrome but our clients are restricted to IE so Chrome is not an option.