D&D Next Character Sheet Jumps When I Make a Roll

When I use one of the Roll buttons, the character sheet jumps down to the equipment section. For example, if I push the button that auto-rolls to make an attack, the screen jumps down to the equipment section, so I have to scroll all the way back up to roll damage if I hit. Is anyone else experiencing this problem?

I'm not seeing any issues and none of my players have reported any issues. I also cant replicate the issue in testing just now. Is this for all of the macro buttons or just a specific one or two?

I figured out what the issue was. In the equipment section I had listed a sling as weighing 0.5 pounds, so every time I went to roll, it went down to notify me that I needed to change that to a whole number. I kinda wish the sheet would allow for weight fractions and had a spot for weight of coins carried.

Ahh cool....i think thats actually the browser enforcing that and it varies from browser to browser. I'll have a look at what I can do when the time comes to update the sheet for the full release of 5e/Next in a couple of months. I dont plan to update the sheet (barring any significant bugs) before then. I'll also add the coin weight....that will be super easy to add and autocalculate so expect that in the full release version of the sheet too!

Actoba said: Ahh cool....i think thats actually the browser enforcing that and it varies from browser to browser. I'll have a look at what I can do when the time comes to update the sheet for the full release of 5e/Next in a couple of months. I dont plan to update the sheet (barring any significant bugs) before then. I'll also add the coin weight....that will be super easy to add and autocalculate so expect that in the full release version of the sheet too! FYI this is another reason to not use number types, just use text there is really no good reason to use numbers.

I dont agree. Proper validation of input helps prevent so many issues particularly when there is auto-calculation involved. The issue is getting the validation correct and, just as important, appropriate for the data you expect or require.

Actoba said: Ahh cool....i think thats actually the browser enforcing that and it varies from browser to browser. I'll have a look at what I can do when the time comes to update the sheet for the full release of 5e/Next in a couple of months. I dont plan to update the sheet (barring any significant bugs) before then. I'll also add the coin weight....that will be super easy to add and autocalculate so expect that in the full release version of the sheet too! Great!! Looking forward to it!!

Actoba said: I dont agree. Proper validation of input helps prevent so many issues particularly when there is auto-calculation involved. The issue is getting the validation correct and, just as important, appropriate for the data you expect or require. Then add step="any" to all of your number inputs but I have no idea how well it is supported, validation is nice but not at the expence of correct functionality.

Most major browsers support the newer HTML5 attributes but differ in how strictly they enforce them and what feedback they give the user (like for example allowing "invalid" inputs but flagging them up to the user whenever a button is used on the form as we see here). Broadly speaking, you should always seek to validate user input appropriately as not doing so is usually a much much bigger problem than a less than ideal usability issue. If done right though, validation shouldn't cause any user issues except when you want it to for invalid input.