Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bootstrap template Validation Error #28

Open
shred3590 opened this issue May 11, 2015 · 3 comments
Open

Bootstrap template Validation Error #28

shred3590 opened this issue May 11, 2015 · 3 comments

Comments

@shred3590
Copy link

There is a validation error issue that shows up in the Bootstrap template. Line 8 of the template has the following line:

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

The validator returns the following error:
A meta element with an http-equiv attribute whose value is X-UA-Compatible must have a content attribute with the value IE=edge.

The example code snippet in the error message looks identical to the Bootstrap snip with the possible exception of the spacing between Compatible" and content.

@cfjedimaster
Copy link
Owner

I'm sorry, what? Are you saying the validator returns an incorrect message? If so, you should file a bug report with https://validator.w3.org/ as that is the remote API my extension uses. I don't think you mean my extension itself as there isn't a file w/ this in it.

@shred3590
Copy link
Author

I am fairly new to programming, so I am not sure who to report to. I will
report there. If I understand it, your Brackets extension takes the
Brackets code and runs it against the w3 validator, so any reports of
invalid code that is actually valid is a w3 issue. Is that correct?

Ted

From: Raymond Camden [mailto:[email protected]]
Sent: Monday, May 11, 2015 4:32 AM
To: cfjedimaster/brackets-w3cvalidation
Cc: shred3590
Subject: Re: [brackets-w3cvalidation] Bootstrap template Validation Error
(#28)

I'm sorry, what? Are you saying the validator returns an incorrect message?
If so, you should file a bug report with https://validator.w3.org/ as that
is the remote API my extension uses. I don't think you mean my extension
itself as there isn't a file w/ this in it.

Reply to this email directly or view it on GitHub
<#28 (comment)
nt-100877329>
.https://github.com/notifications/beacon/AL0bqisjHgh9VkTbdBjOxOwdk0Yn7FPRks5
oIIq0gaJpZM4EWd4H.gif

@cfjedimaster
Copy link
Owner

Well, to be clear, if you use the same inputs at https://validator.w3.org/, and you feel the inputs are wrong, then yes, you need to file it with them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants