andrewtelnov
commented
3 years ago @BryanEuton To be honest, I don't know what is the correct way, using or
It is easy to change the rendering in the code. It will take an hour or less, then couple hours to correct our E2E tests, we have selectors "input[value='Next']" and "input[value='Complete']". We can refactor them and replace with functions. I don't want to do it in minor update, because I am afraid other devs/companies rely on this type of rendering in their E2E testing as well and they would be unhappy to find out that we add this breaking change into a minor version. I would definitely be unhappy, if an author of a third-party library, that I use, did it.
If we understand that the correct way is to use "button" html element, then we will change it in a major version. This breaking change in major version our users/customers will likely forgive us, if we explain why we did it and why it is better.
By the way, you can turn-off the current navigation and use the your own. Here is the example.
FYI: We are working on advanced navigation as well. We will make this type of navigation out of the box.
Thank you, Andrew
Are you requesting a feature, reporting a bug or asking a question?
Asking a question.
What is the current behavior?
The Navigation buttons are input fields instead of buttons
What is the expected behavior?
I've been hooking into the onAfterRenderPage to add buttons and utilizing css to hide the input fields, but is there a way to have a custom navigation html instead? What I would like is to be able to also display some text before and/or after the buttons at times. We use SurveyJS on several of our forms and sometimes the designs show text above or below the buttons.
How would you reproduce the current behavior (if this is a bug)?
N/A
Specify your