Thatâs a poor excuse. IE has a good sized chunk of the market. If I saw a website that forced me to change browsers, Iâd leave and find another website that will give me what I want.
Head over to the HTML and CSS category over here on these forums and weâll patch up the website. Include a link to the problem site, say WHAT VERSIONS of IE have the specific problems, and we will work with you. Be descriptive when identifying problem areas.
If you search, inaddition to MSIE, for âTridentâ then youâll grab your IE11. IE11 stopped using MSIE as a user agent string. Specifically âTrident/7.0â for IE11, or you could just do
Iâd leave and find another website that will give me what I want.
Unless of course, it was say, a website that you were forced to use for work that only accepted particular IE versions, and then we just must grit our teeth and use it, or figure out an elaborate workaround. Weird how that works.
perhaps if you were to update to get rid of long dead code then your site would work better with all browsers.
Anyway you shouldnât be testing the useragentr as that can contain anything and a lot of people running fully compliant browsers have their useragent set to spoof IE because a lot of sites stupidly test for that browser and will not allow you in of you are NOT using it.
Recently, Iâm actually finding I.E. playing nicer lately than Firefox, which for me is a little strange. However, I design for all browsers and periodically check from time to time to see how the website looks on a particular browser. The only one I really get lacks on is Safari.
I still have Safari on my Windows OS.
But as the Windows version of Safari is âdeadâ Iâve been thinking testing with it is pointless unless I do so from within a VM