This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 23023 - The link ”View” refers to http://gitorious.org/microdatajs/microdatajs/trees/master/test which results in 404 Not Found.
Summary: The link ”View” refers to http://gitorious.org/microdatajs/microdatajs/trees/...
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-20 17:11 UTC by contributor
Modified: 2013-08-21 09:33 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2013-08-20 17:11:18 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/microdata.html
Multipage: http://www.whatwg.org/C#microdata-dom-api
Complete: http://www.whatwg.org/c#microdata-dom-api
Referrer: http://en.wikipedia.org/wiki/Microdata_(HTML)

Comment:
The link ”View” refers to
http://gitorious.org/microdatajs/microdatajs/trees/master/test which results
in 404 Not Found.

Posted from: 88.114.31.151
User agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.57 Safari/537.36
Comment 1 Ian 'Hixie' Hickson 2013-08-20 17:48:05 UTC 
foolip, is this yours?

This is referring to the test listed in the status box at:
   http://www.whatwg.org/html#microdata-dom-api
Comment 2 Philip Jägenstedt 2013-08-21 09:18:04 UTC 
Yes, I left a README in https://gitorious.org/microdatajs/ to point to the new location, not realizing that there were any direct links to the contents of the repo. The simplest fix is to point to https://github.com/foolip/microdatajs instead.
Comment 3 Philip Jägenstedt 2013-08-21 09:33:00 UTC 
I've removed the link entirely, since it is only tests for the jQuery look-alike API and not for the proper DOM API. At first I tried to implement the DOM API as is (with mutation observers and whatnot) but gave up on that, together with the tests.