uh, no, those cases don't work... Add CCs now has a button when it didn't previously, the Batch Editor UI is wonky, but I can probably fix that with some CSS.

There's some stuff in tokenizer.css which should probably get cleaned up, too.

Roughly, the idea with the has-browse class is:

• The button is always rendered into the DOM, just invisible by default.
• If a control is browsable, we add has-browse: CSS should then reveal the button.

Specifically, some/all of these rules are probably junk now:

.jx-tokenizer-frame {
  width: 100%;
}

.jx-tokenizer-frame .jx-tokenizer-frame-browse {
  display: none;
}

.has-browse .jx-tokenizer-frame-browse {
  display: table-cell;
}

.jx-tokenizer-frame td.jx-tokenizer-frame-input {
  width: 100%;
}

.jx-tokenizer-frame-browse {
  width: 100px;
  vertical-align: middle;
  padding: 0 0 0 4px;
}

(The unusual way the rendering works is because in Herald we produce a single "template" that needs to be able to generate both browsable and unbrowsable typehaeads, so we always have to be able to have a button to show.)

I can dig it.