W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2013

Re: [admin] If you use `respec`, your ED may be broken

From: Кошмарчик <garykac@chromium.org>
Date: Fri, 25 Jan 2013 10:27:54 -0800
Message-ID: <CAGnkXoEm1XOq1_t5n0ouNBbA2-k9hvLHe0kN5n+yHRx=jtWp0Q@mail.gmail.com>
To: Arthur Barstow <art.barstow@nokia.com>
Cc: public-webapps <public-webapps@w3.org>
On Fri, Jan 25, 2013 at 7:24 AM, Arthur Barstow <art.barstow@nokia.com>wrote:

> Editors that use Respec - if you use Respec, your ED may be broken due to
> a recent change in the way hg/dvcs is configured ...
>
> I noticed at least the following EDs do not properly display the ED's
> boilerplate nor the Status of the Document section: DOM P&S, File API: D&S,
> File API: Writer; Gamepad, IDB, IME, PointerLock, Push API, Screen
> Orientation.
>
> Robin indicated you need to do the following to address this problem:
>
> [[
> instead of:
>
> <script type="text/javascript" src='http://darobin.github.**
> com/respec/builds/respec-w3c-**common.js<http://darobin.github.com/respec/builds/respec-w3c-common.js>'
> class='remove'></script>
>
> use:
>
> <script src='//www.w3.org/Tools/**respec/respec-w3c-common<http://www.w3.org/Tools/respec/respec-w3c-common>'
> class='remove' async></script>
>

This doesn't work well when loading a local respec file since it looks for
file://www.w3.org/... (and fails).  This makes it harder to work on the ED.

It seems safer to just use https when loading the respec-w3c-common file -
that way it works everywhere.
Received on Friday, 25 January 2013 18:28:27 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:57 GMT