Actually, you have no friends I guess...read back your posts...you are trolling EVERYONE commenting on this topic, proving that you are such superior...
Now, I know most people here have barely heard of html or css, much less the things I'm now going to list, but here are some things on that web page that work in ALL modern browsers but do not work in IE9. In addition, some of these things Microsoft has already stated they won't support in IE9: # Application Cache (offline) # Web Workers (threads in JavaScript) # HTML5 Forms (validation mechanism, CSS3 selectors) # JavaScript Strict Mode # ForeignObject (embed external content in SVG) # SMIL Animations (SVG animations) # File API # WebGL (3D) # CSS3 Transitions (for animations) # CSS3 Text Shadow # CSS3 Gradients # CSS3 Border Image # CSS3 Flex box model # ClassList APIs # FormData # HTML5 History API # Drag'n Drop from Desktop
if you want to work seo from your pc you need to download and run Firefox because Firefox give you seo tools
I think you need to read the thread. Or perhaps we should follow this train of thought, and just ask MS to tell us what web standards they'd like us to use ... hey, maybe they could define them as well!
Are you just incomplete? How can you say this is a modern website? Have you ever validated this web page using this http://validator.w3.org ? I think you are just after Microsoft and IE. You really don't know much as you are incomplete in these field? I'll give you some advice. Please follow it. https://demos.mozilla.org/en-US/ Validate this webpage using W3C validator here http://validator.w3.org Check if this is a valid webpage. I have checked this and the result is here: Errors found while checking this document as HTML5! Result: 17 Errors, 3 warning(s) Notes and Potential Issues The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation, or other things affecting the output below. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document. Info Using experimental feature: HTML5 Conformance Checker. The validator checked your document with an experimental feature: HTML5 Conformance Checker. This feature has been made available for your convenience, but be aware that it may be unreliable, or not perfectly up to date with the latest development of some cutting-edge technologies. If you find any issues with this feature, please report them. Thank you. ↑ Top Validation Output: 17 Errors Error Line 4, Column 51: Attribute xmlnsg not allowed here. xmlns:fb="http://www.facebook.com/2008/fbml"> ✉ Warning Line 4, Column 51: Attribute with the local name xmlnsg is not serializable as XML 1.0. xmlns:fb="http://www.facebook.com/2008/fbml"> ✉ Error Line 4, Column 51: Attribute xmlns:fb not allowed here. xmlns:fb="http://www.facebook.com/2008/fbml"> ✉ Warning Line 4, Column 51: Attribute with the local name xmlns:fb is not serializable as XML 1.0. xmlns:fb="http://www.facebook.com/2008/fbml"> ✉ Error Line 17, Column 11: Bogus comment. <![if gte IE 9 ]> ✉ Error Line 19, Column 14: Bogus comment. <![endif]> ✉ Error Line 25, Column 82: Attribute property not allowed on element meta at this point. … <meta property="og:title" content="Mozilla's Web O'(pen) Wonder"/> Attributes for element meta: Global attributes name http-equiv content charset Error Line 25, Column 82: Element meta is missing one or more of the following attributes: http-equiv, itemprop, name. … <meta property="og:title" content="Mozilla's Web O'(pen) Wonder"/> Attributes for element meta: Global attributes name http-equiv content charset Error Line 26, Column 52: Attribute property not allowed on element meta at this point. <meta property="og:type" content="website"/> Attributes for element meta: Global attributes name http-equiv content charset Error Line 26, Column 52: Element meta is missing one or more of the following attributes: http-equiv, itemprop, name. <meta property="og:type" content="website"/> Attributes for element meta: Global attributes name http-equiv content charset Error Line 27, Column 70: Attribute property not allowed on element meta at this point. <meta property="og:url" content="https://demos.mozilla.org/"/> Attributes for element meta: Global attributes name http-equiv content charset Error Line 27, Column 70: Element meta is missing one or more of the following attributes: http-equiv, itemprop, name. <meta property="og:url" content="https://demos.mozilla.org/"/> Attributes for element meta: Global attributes name http-equiv content charset Error Line 28, Column 107: Attribute property not allowed on element meta at this point. …" content="https://demos.mozilla.org/media/img/facebook_like_500x312.png"/> Attributes for element meta: Global attributes name http-equiv content charset Error Line 28, Column 107: Element meta is missing one or more of the following attributes: http-equiv, itemprop, name. …" content="https://demos.mozilla.org/media/img/facebook_like_500x312.png"/> Attributes for element meta: Global attributes name http-equiv content charset Error Line 29, Column 86: Attribute property not allowed on element meta at this point. … <meta property="og:site_name" content="Mozilla's Web O'(pen) Wonder"/> Attributes for element meta: Global attributes name http-equiv content charset Error Line 29, Column 86: Element meta is missing one or more of the following attributes: http-equiv, itemprop, name. … <meta property="og:site_name" content="Mozilla's Web O'(pen) Wonder"/> Attributes for element meta: Global attributes name http-equiv content charset Error Line 31, Column 137: Attribute property not allowed on element meta at this point. …capable of? Explore the Web o' Wonder demo gallery and prepare to be amazed!"/> Attributes for element meta: Global attributes name http-equiv content charset Error Line 31, Column 137: Element meta is missing one or more of the following attributes: http-equiv, itemprop, name. …capable of? Explore the Web o' Wonder demo gallery and prepare to be amazed!"/> Attributes for element meta: Global attributes name http-equiv content charset Error Line 651, Column 104: & did not start a character reference. (& probably should have been escaped as &.) …illa.com/en-US/mobile/download/?WT.mc_id=webwonder&WT.mc_ev=click">Mobile</div>
And, again, the DP braintrust arises and brings up a five month old thread. Completely ignorant of modern standards and practices, they are oblivious. That validator is not as up to date as the newer, better HTML5 Validator which I'm sure you are totally unaware of. Even that one doesn't catch all the newer elements and properties available in modern browsers today (and of course not IE). Ah the standard Microsoftie response. "Microsoft hatred" is the reason the page doesn't work in IE and not the fact that the markup won't work in IE because IE can't run it. All that markup is completely documented by the W3C and WHATWG and works in ALL modern browsers but the fact that it doesn't run in IE is only due to "Microsoft/IE hate" and no other reason. See what I just typed and then tell us who is "incomplete".
This reply shows how much incomplete you are. You are saying "All that markup is completely documented by the W3C" Here you are 50% incomplete. You should know this is W3C Validator http://validator.w3.org. And as per your validator result : Error: Attribute xmlnsg not allowed here. From line 1, column 16; to line 4, column 51 TYPE html>↩<html LANG="en-US" dir="ltr" ↩ xmlnsg="http://ogp.me/ns#"↩ xmlns:fb="http://www.facebook.com/2008/fbml">↩ <he Warning: Attribute with the local name xmlnsg is not serializable as XML 1.0. From line 1, column 16; to line 4, column 51 ......................................... ......................................... ............................................... There were errors. (Tried in the text/html mode.) Total execution time 862 milliseconds. Note: Before posting an incomplete data think 100 times. Check 2 times before posting what are you posting. You haven't checked the validation of the web page and posting with unrelevant arrguements. I was thinking you are 30% incomplete. But your reply to my post shows you are 100% incomplete.
Here you show you are ignorant. You are trying to compare the documentation to the validator. The validator is far behind the documentation of the new elements. You want the validator to validate new implementations but you don't understand that that won't happen. If you can't figure that out, then it's no point arguing with you. As I said, EVERYTHING will work in ANY modern browser but it WON'T work in inept, incompetent, backwards IE. Documented, proven, verifiable.
Cause you didn't use a modern browser and only IE so you missed out on most of the functionality available to those of us who use modern browsers (never IE). But IE users are used to missing out and not knowing the difference.