Clickable up and down arrows not working on number input fields

On my sheet, I have an attribute table. The 'derived' attribute column appears to be working fine. But for the attributes to the left, as soon as I try to click on the up or down arrow of an attribute, the arrows disappear and nothing happens. I have to manually type in a number.&nbsp; I've tried troubleshooting a little, but I really don't know where to begin. The code is a little bit too long for that table to share here. And since I'm not sure what part of the sheet might be causing this (perhapse even a sheetworker?) here's a link to the whole sheet. <a href="https://github.com/danimagaming/dodas-sheet_troubleshooting/tree/main" rel="nofollow">https://github.com/danimagaming/dodas-sheet_troubleshooting/tree/main</a> Html: Attribute table - line 31&nbsp; &nbsp; CSS: Attribute table - line 150 Edit: I checked in Firefox as well, and have this problem in both firefox and chrome. But in firefox, the arrows appear but clicking on them doesn't do anything. The sheet worked fine before I made the change to the CSE upgrade, so I suspect it has something to do with that. Sorry for linking to a bunch of code. Thanks for any help!

I havent looked at the sheet, but from the description, this sounds like a CSS issue.That's where you should be looking. It cannot be a sheet worker issue - the javascript allowed cannot make changes like this. Regarding CSE being the culprit: it might be, kind of, indirectly. CSE made a lot more HTML and CSS available. The code before CSE might have included whatever is causing this issue, but it was not supported so it wasn't working. Then when CSE was added, that code started working and had the effect you are seeing. So it's not that CSE is the issue, it merely made something possile that wasn't before. (That's my guess anyway.)

Hmm. Thanks, I can try digging into the CSS around the attribute table.&nbsp;

I compared the entirety of the CSS styling applied to each in the Chrome developer tools window, and also checked if any styling was different. But they both have the exact same CSS styling applied. That is, both are just the 'input' styling. There doesn't appear to be anything else getting applied different from the two.

Nevermind, I figured it out. It turns out I had a div element in the middle of the row called 'blank row' (no clue why I put it there), should've called it blank cell or divider or something. Anyways, something in roll20 automatically applied a styling to it with 15px padding, which covered up the input field. If I unselect it it works. Perhaps a bootstrap type thing, or something similar? I changed all of those div instances that I used as a divider by calling the class 'attributeDivider' and it works fine now. That was the first thing I coded and didn't really know what I was doing. Not the best semantic choice, and apparently one with some automatic styling getting applied.

Aha, well done. Roll20's native styling can often be a problem, and ot's good to learn how to remove it.

Agreed. It's a new adventure since converting to CSE, learning all the native styling I often have to work around. Not the first encounter haha. Thanks for the input!