How to solve http-equiv validation error from W3C Validator?

HTML & CSS
1

I am not able to validate the first line under the <head> line in my page

<!DOCTYPE html>
  
<html prefix="og: http://ogp.me/ns#" lang="en-GB">

<head>
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />

<meta charset="utf-8">

<title> Sydney hotels, Sydney airport, tipping, travel insurance</title>
<meta name="viewport" content="width=device-width; initial-scale=1.0">

I get

Validation Output: 1 Error
Line 6, Column 64: A meta element with an http-equiv attribute whose value is X-UA-Compatible must have a content attribute with the value IE=edge.

2

With that chrome=1 on there it’s making it invalid. However not all invalid code is “invalid” per say.

Chalk this up to the validator being stingy.

</thread>

3

Hi Ryan

It’s Workers Day. You’re not supposed to work!

Your post seems to have been truncated.

Meanwhile I found this and could go the .htaccess way. What do you think?

http://www.validatethis.co.uk/news/fix-bad-value-x-ua-compatible-once-and-for-all/

4

Leaving at 1400 for the beach (well I’m doing a half marathon down there so it won’t really be a vacation…)

Besides, I code at work - that’s not “work” if I love doing it :wink: .

I think you should listen to the tweets that are mentioned there when they say to just not worry about it.

Noone cares if your site is invalid due to that extra value.

5

Boy, you’re getting on! What happened to the full Marathon?

Anyway, back to the .htaccess- Do you think that’s a good idea? I like to validate whether it really matters or not…

6

Depends on if your apache has that module enabled. If you are on shared hosting (most likely), and it’s not enabled (probably not), you probably won’t be able to use it.

Overall - no I don’t think it’s a good idea because you shouldn’t care whether it validates.

7

ok, but it’s like the marathon:: it’s the participating, not the winning

Don’t go too fast. You might get tired and then be unable to help me for a quite a few days!

8

Hi Ryan

I’ve just had a search in my site and have a load of files with similar code that passed the validation.

The only difference is that it does not contain the Chrome bit.

<meta http-equiv="X-UA-Compatible" content="IE=edge" />

Is that Chrome bit important? Otherwise I solve the validation by simply deleteing it.

9

I already said that the chrome value was making it invalid :wink: .

10

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.