- From: Robin Berjon <robin@w3.org>
- Date: Thu, 11 Oct 2012 12:02:12 +0200
- To: Shane McCarron <shane@aptest.com>
- CC: spec-prod@w3.org
On 11/10/2012 11:37 , Shane McCarron wrote: > The problem I am seeing right now is that the core util tests are all > failing. And they are failing because the 'require' statement is > failing. Basically it does not think the util.js is getting loaded. I > don't know why it doesn't think this because it clearly gets loaded > once. But then there is a second attempt to load it (according my local > apache log) and that attempt uses an incorrect URI (/js/core/utils.js) > for some reason. That's weird. It all runs fine here. If utils.js don't load a lot of the rest should fail too. Is it possible that your server's configuration has a problem? > While I have your attention, is there a way to tell what version of > respec actually gets served up by the W3C Tools/respec/respec-w3c-common > ? Yes, the comment at the top of that file has the version number. It currently says: /* ReSpec 3.1.27 - Robin Berjon, http://berjon.com/ (@robinberjon) */ If you're seeing something else, you likely have a cache problem. > It doesn't seem as if the diffmark stuff is being included when > respec loads from there. At least I can't make it appear from there, > but when I work locally it appears (when I press ctrl-alt-shift-S). Strange. Do you have a pointer to a document in which it doesn't work? -- Robin Berjon - http://berjon.com/ - @robinberjon
Received on Thursday, 11 October 2012 10:02:17 UTC