Shard said:
Nope, made no difference. And even if that was the problem, I have done it a bazillion times before over the past few years with np whatsoever. This seems to clearly be a problem with the recent updates.
The problem with that assumption is that the platform is continually developing. Any recent issue can easily be attributed to "recent changes", so it gets us no closer to a cause unless the problem is both sudden and widespread. This is the first report I can remember seeing of this particular phenomenon and no one else seems to be reporting it. So the first recourse is to look for issues about how a user's computer is locally or uniquely reacting to Roll20 code.
I.e. it may or may not be a Roll20 code issue, but what makes it behave differently on your machine? I do notice that the two repeating areas that lack the controls or display, also have the resize controls in the area (se below), indicating that the whole area is being interpreted as a text field, rather than a repeating container. This is not normal.
This is a first level fighter. Have you added any third party (non-WotC) compendium sources to the game? It could be a case of bad data from a third party compendium breaking the HTML.
