Is there any way how to programmatically (thru HTML or asp.net or C# etc) add or activate(add-on) spellchecker to IE 8 (could be also IE9 or IE10 but with doc mode IE8 ) ?
I know, that by default IE 8 dont have spellchecker included.
I guess there is this however there's no real other way unfortunately.
http://www.iespell.com/
Related
In my API response body I'm having . while this doen't create any issue in chrome/firefox.
While rendering in IE 8, I'm seeing 'undefined' in my UI.
I'm using Angular 8. and i'm already using utf-8 encoding in my index.html
<meta charset="utf-8">
Any idea what is causing the issue? Is it a Angular 8 IE bug?
As per the official document, Angular is supported in IE 9, 10, 11 versions. you are using the IE 8 that is not supported.
So I am not sure how your angular app is working in the IE 8 browser.
This can be a possible cause of this issue.
If you think that this is not the case then I suggest you try to provide the detailed information with some sample code and detailed steps for producing the issue and test the issue to check for the results.
Another thing I want to inform you that IE 8 is a too old version and it is out of support scope of Microsoft. I suggest you use the latest Microsoft browser or at least move to the IE 11 version.
I noticed that in IE 11, select fields (dropdowns) have a diffent appearance (and the other form fields looks different as well). It looks flat on IE 11 while on other browsers (even lower IE browsers), it is not.
Is this an effect of Window's Metro UI which is only available on Windows 8? If it is then why am I experiencing it on Windows 7?
Is there a way to force form fields to use older ui? I've used <meta http-equiv="x-ua-compatible" content="IE=9" > but it does not work.
Please refer to this link for a live sample. Use IE 11 please.
http://jsfiddle.net/u8xtumya/
Yes, this is the way select are being styled by IE11. This might or might not be directly related to the Metro UI, but that doesn't matter.
Setting an older compatibility mode will not affect the looks of elements. It will make sure you miss out on functionality that has been added to IE11 that was not present in older versions. It's a bad idea to use anything but the latest compatibility mode if there's not a very good reason to do so (like your web app is old and doesn't run in the latest version).
You can use CSS to style the select (and the ::-ms-expand pseudo-class to style the arrow that expands the menu)
IE is not recognizing % entity in both 8 and 9 versions. I tested in two computers.
I read that it is implemented in IE here:
http://code.google.com/p/doctype/wiki/PercntCharacterEntity
Any idea?
Thanks
According to the HTML ASCII Reference you can just use %, IE should play nicely with that :-)
Strangely though, according to the Google doctype wiki % is supposed to be supported in all versions of IE from 6 to 8, so it should work in IE8
Good day! I have got a question about the Internet Explorer 9. Can anyone tell me if its document and browser mode (I mean rendering as Internet Explorer 8 and 7 when chosen) is appropriate to test HTML and CSS in different versions of the browser?
I used to use something like Multiple IE on my virtual Windows machine, but my colleague use the Internet Explorer 9 to test HTML and CSS "directly". So none of us has a sense of correctness of the chosen solution.
So, that's the question.
In my subjective experience, IE9's 8/7 "Browser Modes" have always been an accurate reflection of the actual browsers - at least for pure HTML/CSS.
However, there are subtle differences when it comes to JavaScript, see the "Differences between IE8 Compatibility View and IE7" section here:
http://blogs.msdn.com/b/ie/archive/2009/03/12/site-compatibility-and-ie8.aspx
I usually test with IE9's older "Browser Modes", but if I'm feeling paranoid or I want to be absolutely sure, I use my virtual machines.
IMHO the answer to your question is yes - go with the browser modes.
Here is a good article for you
http://blogs.msdn.com/b/ie/archive/2010/10/19/testing-sites-with-browser-mode-vs-doc-mode.aspx
Few differences that I have seen in IE9 Doc Mode vs real IE8 or IE7:
1) If a PNG image is given opacity (via Proprietary CSS filter), 'Real IE8/IE7' shows black linings.
2) JavaScript performance in 'Real IE8/IE7' is obviously not as fast as IE9.
3) Fonts also tend to have some display issue in various modes: http://blog.typekit.com/2013/03/14/the-dangers-of-cross-browser-testing-with-ie9s-browser-modes/ and font smoothing is an issue in windows XP.
4) Embedded YouTube videos have z-index issues overlapping other elements (fixed by wmode).
5) Proprietary CSS filters work properly in 'Real IE8' but are not shown if applied to an HTML5 element in IE9 doc mode. (Faced this once)
Summary: If the site you are making is JavaScript intense or the client is very much concerned about users on IE7/8, have a check on Real IE 7/8 and get the issues ironed out.
I'm making a site for European client and he said Firefox 3 and IE 7 and 8 has more user than others browser for desktop in Europe http://gs.statcounter.com/#browser_version-eu-monthly-200812-201001-bar
I've only IE 7 and Firefox 3.5.7 installed in my PC.
Should I download portable Firefox 3.0 and test in it too even if I'm not using any new css property/selector which only has support in Firefox 3.5 or testing in 3.5.7 would be enough?
And for IE testing in IE 7 would be enough or should i check my site in IE8 (downloading VPC image of IE8 and testing in VM) even if I'm not using any new css property/selector which only has support in IE8?
Or is it necessary to use <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" /> in <head> ?
But what will happen when user will switch compatibility mode to IE 8 default rendering mode?
Can we make site compatible in IE 7 and 8 both without using <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />? If yes, then what special we need to do.care/consider in css to make site identical in both?
It's worth testing the site in all browser to ensure that it is working correctly. Another way to test is to use the browser sandbox here: http://spoon.net/browsers/
IE8 is alot more standards compliant then previous versions of IE so if you are designing for FF 3.5 then you shouldn't have too many problems with IE8. It's worth using conditional comments as Dough mentioned to target IE7 or IE6 - http://www.quirksmode.org/css/condcom.html
Consider using this website checklist - http://www.xs4all.nl/~sbpoley/webmatters/checklist.html as once you have validated your html and css and gone through most of the other points then you will be well on your way to having the site display properly across all browsers
You don't necessarily need to download all the copies, but yes, there is a larger possibility of a difference between IE7 and IE8, though they should be minimized if not eliminated by your meta tag. I highly recommend you don't use that meta tag and just check for differences that might be able to be easily fixed. Since IE8 has come out, I have never had to use the meta tag to fix any problems or differences. I still use IE conditional comments to add rules for fixing differences in IE6 + IE7.
There is much less of a concern between Firefox 3 and 3.5 if you are not using CSS3 or -moz specific selectors.
Either download IETester (IE only) or used Adobe Browser Labs (both) to check IE8 and Firefox 3 as a precaution before launch.
I do dev testing using IEtester, been using it for about a year and it's been 100% correct in rendering CSS when compared to the stand alone versions of IE6,7,8. It's also very good for tweaking CSS and quickly seeing the impact.
From a general perspective I normally have alot more issues between IE6 and other browsers, while IE7 and IE8 are very similar in most regards.