Last modified: 2014-03-21 18:20:38 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T64889, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 62889 - Validation issues with meta tags
Validation issues with meta tags
Status: RESOLVED DUPLICATE of bug 62886
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-03-20 19:25 UTC by Jon
Modified: 2014-03-21 18:20 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Jon 2014-03-20 19:25:46 UTC
1) Bad value X-UA-Compatible for attribute http-equiv on element meta.",

2) link rel="edit" should be an absolute URL. Bad value edit for attribute rel on element link: Not an absolute URL. The string edit is not a registered keyword or absolute URL.

The markup causing these issues is as follows:
<link rel="edit" title="Edit" href="/w/index.php?title=W3CValidationTest&amp;action=edit" />
<meta http-equiv="X-UA-Compatible" content="IE=EDGE" />

These should at the very least be moved out of OutputPage into the skin or be configurable via OutputPage->setProperty. The mobile skin has no need for the X-UA-Compatible meta tag and wishes to use HTML Validation tests as part of its continuous integration testing to catch problems such as unclosed tags.

On a side note: headElement should do with a massive refactor and imo should probably be part of Skin.php so that it can be tweaked where necessary.
Comment 1 Derk-Jan Hartman 2014-03-21 18:20:38 UTC

*** This bug has been marked as a duplicate of bug 62886 ***

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links