Modify the glossary cleanup code to ensure that aliases for terms work the same as a term

[jnurthen]

From @halindrome on August 5, 2015 17:30

If a term is defined and not referenced, that term is removed from our specs. When a term is referenced as an alias, that term might not get preserved correctly. We need to fix this.

Copied from original issue: w3c/aria#76

[jnurthen]

@halindrome Is this ARIA or should this be somewhere else?

[jnurthen]

Move to aria-common?

[michael-n-cooper]

MC to provide steps to reproduce, then Joanie thinks she can fix.

[joanmarie]

@michael-n-cooper: Ping re steps to repro. Thanks!

[joanmarie]

As with the other issue, I tried to come up with steps to reproduce myself and failed. Here's what I tried, using a local copy of Core-AAM:

Because "owning element" is a term not referenced in the Core AAM, and not being included in the terms list, I did the following:

• As a sanity check, I added <a class="termref">owning elements</a> to the spec text. Result: this term got added as expected.
• As an attempt to reproduce what I think is being described in the opening report, I removed my sanity check entry, replacing it with <a class="termref">owning</a> element. ("owning" is one of the aliases in terms.html). Result: this term got added through the use of the alias.

So @michael-n-cooper, if you can reproduce this issue, steps to reproduce would be super helpful. Thanks!