Re: [a11yapi] Patterns (#28)

> +          inherits properties of both of them then the web author should
> +          integrate the new role into existing role hierarchy.
> +        </p>
> +      </section>
> +    </section>
> +    <section>
> +      <h2>
> +        Extension to the <code>AccessibleDocument</code> interface
> +      </h2>
> +      <p>
> +        An <a>accessible document</a> provides a method to import taxonomies.
> +      </p>
> +      <pre class="idl">
> +partial interface AccessibleDocument {
> +  Taxon? taxonOf(DOMString taxonomy, DOMString name);
> +  [ Throws ]

> If I do the work in parallel, then what is a better way to avoid confusion? 

Always make sure you branch from gh-pages. Not sure what happened here where you ended up with both 
patterns and taxonomies. 

> Should each branch be positioned against master gh-pages?

Yep :+1: 

>  What is a best analogue of MQ in git where I was able to stack patches on top of each other?

Yeah, basically do:

```
git checkout gh-pages
git checkout -b myFirstFeature
... do a bunch of work.... git commit.... 
git push origin myFirstFeature
# Switch back...
git checkout gh-pages 
git checkout -b myOtherFeature
... do a bunch of work.... git commit.... 
git push origin myOtherFeature
```

And so on... that way, you keep things separate.

---
Reply to this email directly or view it on GitHub:
https://github.com/WICG/a11yapi/pull/28/files#r45589514