I'm using in my website some of the Telerik controls. (framework 2) Now i need to change the meta line to:
<meta http-equiv="X-UA-Compatible" content="IE=9">
instead of:
<meta http-equiv="X-UA-Compatible" content="IE=7">
For css compabilty(for border radius and other things), when i change this line, the telerik controls in some pages are not looking good.
Does anyone have any idea?
Because the stylesheet streamed out from Telerik.Web.Resource.axd handler does not set the mime type properly and IE9 ignores stylesheets without proper mimetype set.
I am not aware of any solution for it except adding the IE7 compatibility meta tag.
Solution:
Create a new code file and add the embedded stylesheets with the assembly code as below.
[assembly: WebResource("Assets.Skins.Calendar.Custom.css", "text/css")]
Related
Reaching out to see if any ADA compliance experts might know how I might resolve an ADA compliance issue pertaining to our video transactions. We essentially provide links to .txt files for all of our videos which contain the video transcription. But when running an ADA scan we receive 2 errors pertaining to our transcriptions.
"Language missing or invalid "
"Missing or uninformative page title"
I'm not sure how I would tell a screen reader or ADA scanner the language or a page title given that these are just plain txt files. Any assistance would be greatly appreciated. Thanks.
This might be more about how your browser is set up to handle .txt files. Is your default action to download the file or to view it in the browser?
If the file is downloaded, then it's up to the end user to display the .txt file in whatever program they have set up to view them.
If you're letting the browser display the page, then that page is generated by the browser and I'm not sure if you can customize the page that's generated. I tried Firefox, Chrome, and Edge and they all generated a similar template to view a text file. (Edge uses the chromium engine so it's not surprising that Edge and Chrome have the same template). There's just a minor difference in the <head> between Firefox and Chrome.
This is essentially what's generated:
<html>
<head>
<!-- if using firefox -->
<link rel="stylesheet" href="resource://content-accessible/plaintext.css">
<!-- if using chrome/edge -->
<meta name="color-scheme" content="light dark">
</head>
<body>
<pre>
(contents of text file)
</pre>
</body>
</html>
If you run an accessibility scanner on this generated page, you will indeed get the two errors you mentioned.
3.1.1 Language of Page
2.4.2 Page Titled
For the language, that's specified on the <html> element with the lang attribute. If you bring up the code inspector on this stackoverflow page, you'll see lang="en":
<html class="html__responsive " lang="en">
For the page title, that's specified in the <head> with a child element of <title>. You can also see that in the stackoverflow page:
<head>
<title>wcag - ADA Compliance Language Missing or Invalid for video transcription txt files - Stack Overflow</title>
...
</head>
If no page title is specified, the browser usually shows the URL or just the filename as the title.
So, can you do anything about the template? I'm not sure. That would be an interesting project.
An alternative is to have your own webpage display the text file, which you would obviously have complete control over and could specify the language and the page title. But I would make this a lower priority issue over other accessibility issues that your website might have.
I am building a chat application using Meteor for Android. I have included "Add Image" option using cordova camera plugin. Now, after the image is uploaded and is seen by the users, I want to click on it and zoom it. How to proceed?
Here's my image rendering code :
<div class="message">
<img src="{{t.img}}"
data-action="zoom"
class="showImage"
>
</div>
I've tried using the inno:zoom package but was unsuccessful. Any insights?
In the html head, i have the following code :
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=1">
<link rel="stylesheet" type="text/css" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css">
I’d suggest using a touch library such as Hammerjs: http://hammerjs.github.io/
There are a lot of ways to work with touch in JavaScript, but they can be difficult if you aren’t experienced with them.
You may have to put the uploaded image in its own template and use reactive variables to re-initialize the image element in order to enact the zoom feature. This is likely also true of the package you already tried.
If you could share more code samples, I (or others) might be able to give a more specific answer.
I have a page using the mixitup jquery script.
It works perfectly in Chrome, Opera and IE11.
But I need it to work in IE8 too.
I have the script working in IE8, just without the fancy animations, which is fine.
Except, it only works in IE8 when I set the browser compatibility view to 'Internet Explorer 8 Compatibility View'.
In the screenshot below, it shows different version, but you can see what option I mean, the second one rather than the first one.
I have tried entering the following meta to the top of page:
<meta http-equiv="X-UA-Compatible" content="IE=Edge,chrome=1">
and also:
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE8" >
But both those just seem to force the 'Internet Explorer 8', the equivalent to the top options in the screenshot... not the second one, which I need.
Can that be done?
thanks
If I understand your question correctly then may be below explanation will help you.
Using <meta http-equiv="X-UA-Compatible" content=" _______ " />
The Standard User Agent modes (the non-emulate ones) ignore <!DOCTYPE> directives in your page and render based on the standards supported by that version of IE (e.g., IE=8 will better obey table border spacing and some pseudo selectors than IE=7).
Whereas, the Emulate modes tell IE to follow any <!DOCTYPE> directives in your page, rendering standards mode based the version you choose and quirks mode based on IE=5
Possible values for the content attribute are:
content="IE=5"
content="IE=7"
content="IE=EmulateIE7"
content="IE=8"
content="IE=EmulateIE8"
content="IE=9"
content="IE=EmulateIE9"
content="IE=edge"
If meta tag solution wasn't working for you then set it
header('X-UA-Compatible: IE=edge,chrome=1');
My Application is compatible only with IE8.So, whenever we open the page,Broswer Mode should set automatically to IE 8,instead of going to developer tools and setting there
I always use
<meta http-equiv="x-ua-compatible" content="IE=EmulateIE8" >
this needs to get in the head tag.
You need to add a meta tag to your document head specifying IE8 compatibility mode.
<meta http-equiv="x-ua-compatible" content="IE=8" >
I am currently using an XHTML 1.0 transitional doctype on my vBulletin website. The page in question is PHP. The source (view source) of this page verifies that the XHTML 1.0 transitional doctype is on the page. Upon downloading (File > Save As) the page in IE8, I realized that my doctype had been replaced with an HTML 4.0 transitional doctype.
Why does IE8 change the doctype?
Why isn't the doctype its chosen displayed in the "View Source"?
The answer lies in the global vBulletin options menu.
vBulletin Options -> Cookie and HTTP Header Options -> Send Internet Explorer 7 Compatibility Header (Yes/No)
Disabling that will prevent IE8 from rendering as IE7, and from using the 4.0 HTML transitional doctype.
Please check which Document Mode Your IE8 is running in. If it is IE8 then its some other error. If it's something else than IE8 please add this meta tag as the first element of the <head> Tag.
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />