I'm having some trouble, as usual, with making my html and jquery work on IE7.
I got no problems when i set the document mode in the developer tools to IE8-Standards, using IE7 as browser mode, but i don't know if a native IE7 can do the same.
Has anyone got experience using this mode?
No, IE 7 does not support rendering pages like IE 8.
That would require a time machine. IE 8 and its "standards mode" hadn't been invented at the time that IE 7 was released.
Related
We did some experiments loading sample HTML pages in to the latest version of WPF Web browser control which comes with VS 2017 IDE. Seems perfect in most of the cases except when loading following URLs which throws error messages, which is not the case in modern web browsers like IE, Chrome.
E.g.
1. Error message for W3Schools:
Error message for HTML5Rocks :
Please let us know whether WPF browser control is perfect enough to render/support modern web technology features in our desktop application projects?
-Thank you
I believe the "modern" browser experience on Windows in Microsoft Edge. You could use the WebView control to use it in your WPF application as explained in this blog post. This assumes you are targeting the April 2018 release of Windows 10 or later.
If your users are still in Windows 7, you may want to look for a third-party browser control such as for example CefSharp.
So I have a website and I mean to make 2 version of it, the desktop version (with full features) and mobile version (simplification of the desktop version). I'm using media query in CSS to adjust the style. It works well in native browser. When I open my web using native browser it will show the mobile version style. But somehow when I open my web using Opera Mini, it keeps showing the desktop version instead.
I have googled it and didn't found any clue. Any idea how does it happen?
Thanks!
I finally found what's wrong with it. Turns out I was stupidly using #media screen only and Opera Mini doesn't seem handle it well. I've googled it for hours. Someone said actually Opera Mini supports #media screen but other people said that the right media property for Opera Mini is #media handheld. Well, I tried to play safe by simply changing it to #media all. And it works!
There are a number of reasons why Opera Mini is showing the desktop version of the site. The most likely is that your website is not properly detecting Opera Mini as a mobile site and is not returning the correct content. If you're using some plugin or other piece of software that is automatically handling the routing of desktop vs. mobile for you, that might be the culprit. Also, it's possible that this is happening by design, because of how Opera Mini works.
Opera Mini runs web content through Opera's own proxy servers and attempts to 'optimize' the content before delivering it to the user. That is, content is rendered first on the proxy server and then delivered to the device. This of course creates all kinds of complications for someone who is trying to deliver a consistent mobile web experience to their users. Fortunately, Opera provides a development guide to help give you a better sense of what's going on and how to cope with it.
Opera Mini is, in my experience, a very difficult browser to work with. At the Wikimedia Foundation, we server a very limited Wikipedia (and sibling project) experience when we detect someone's using Opera Mini.
You should definitely read through the opera mini development guide and make sure that any device detection you're doing is correctly recognizing opera mini as a mobile browser. If you're just using media queries, you may either want to reconsider a more robust approach to mobile detection, or adjust your design accordingly to work for opera mini. Good luck!
As I understand, When you run a silverlight application (atleast for case of IE), there is a mini-CLR that build within IE that run as part of the silverlight application.
What happen if I am using some other browser like FireFox, Chrome or Safari. Does these browsers also have CoreCLR embedded within? May be I am just no clear about the architecture as how CoreCLR engine is hosted within different browswers and any info/links will be helpful to understand it.
Silverlight is run in browsers using a browser plug-in, in much the same way as with Flash. To quote the Wikipedia page for Silverlight:
The run-time environment for Silverlight is available as a plug-in for most web browsers.
Once you've installed the plug-in, you can use Silverlight in IE, Firefox and Chrome. The Wikipedia page I linked to above suggests Safari might not support Silverlight, but I haven't tested that.
Does Silverlight work with IE 6, are there any gotchas?
Just wondering if this is an alternative for customers stuck with IE 6.
I have worked on sites that run on IE6 and we were able to work well in Silverlight. As Silverlight is a Plugin, it doesn't matter what they underlying browser is, as long as it is the once supported by Silverlight team. We didnt come across any issues, we had worked on data driven app.
For client OSs the answer is yes
More detail on wikipedia about compatible OSs and browsers
Does anyone know if silverlight plugs into chrome, or when they plan to support it?
This guy have had partial success with silverlight in chrome, but it does not seem to be supported:
http://wildermuth.com/2008/09/02/Silverlight_2_and_Google_Chrome
From The Microsoft Silverlight Team in the silverlight forum:
Hello, currently we don't have plans
to support Chrome. We will support it
in the future if it gains enough
market share. Please understand, each
browser implements the plug-in model
differently, so it'll be a lot of
effort to officially support a browser
100%... By the way, IE 8 also runs
each tab in its own process. If a tab
crashes, other tabs will still work
fine.
UPDATE:
Jon Galloway has just posted instructions on how to get silverlight successfully running on Chrome here:
http://weblogs.asp.net/jgalloway/archive/2008/09/17/silverlight-on-chrome.aspx
The official word on what is supported looks like this:
alt text http://www.jesseliberty.com/sl/browsers.jpg
The reality is that we do run on a lot of browsers, but things change might quickly in these here parts.
For what it is worth, the Dev Branch of Google Chrome was recently updated to support Silverlight 2. I tried it and it works for me. Of course, you have to use the Dev release of Google Chrome. You can get more information about switching to Chrome Dev here.
Silverlight already works with web-kit, and since Google's Chrome is based on web-kit, it shouldn't be too much effort to get it working.
Indeed, this gentleman seems to have had some success.
Based on this, I would suspect that Silverlight will be fully supported by Chrome by the time it goes gold.