Re: ReSpec broken for all(?) specs except ARIA, in some browsers

Arrgh.  Okay - thanks for letting me know.  Marcos has changed all sorts of
things.  Who knows which broke extensions?  I will work with him to figure
it out.

On Thu, May 26, 2016 at 6:45 AM, Joanmarie Diggs <jdiggs@igalia.com> wrote:

> ARIA is broken too. Noticeably so. Roles lack their previous formatting
> and "placeholder" shows up in the tables whereas before those cells were
> populated.
>
> --joanie
>
> On 05/25/2016 10:09 PM, Amelia Bellamy-Royds wrote:
> > Both on my local copy and from RawGit, for all the AAM and other specs,
> > Respec is not running successfully.
> >
> > The 2 scripts appear to be running in the wrong order. In Chrome and
> > Edge, the console gives me an error from resolveReferences.js (Uncaught
> > ReferenceError: respecEvents is not defined), followed by an error
> > from respec-w3c-common (Uncaught TypeError: Cannot redefine
> > property:  respecEvents).  In Firefox, the second error doesn't fire &
> > so the specs build with various other errors caused by the first script
> > being aborted.
> >
> > Does anyone know why the main ReSpec script would be loading
> > asynchronously all of a sudden?  Or has it been doing that all along,
> > and the errors were simply not fatal enough to notice?
> >
> > ARIA 1.1 compiles correctly, if slowly. The only difference seems to be
> > that it has another local script (aria.js) blocking the
> > resolveReferences.js script.
> >
> >
> >
> > ~Amelia
> >
> >
>
>
>


-- 
Shane McCarron
Projects Manager, Spec-Ops