You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In one of the previous versions a breaking change with HtmlInput.setAttribute was introduced.
Currently, when changing type of HtmlInput a new instance is created and the instance worked on is no longer attached.
Looks like this behavior is intended but causes undesired side effects as the user has absolutely no way knowing they are working on a stale object.
(HtmlElementBuilder is a helper class we created, it basically just creates a StringWebResponse and passes it to to PageCreator)
As a user an UnsupportedOperationException when passing type to setAttribute to force us to use changeType would have been friendlier but I'm not sure how viable that is.
In one of the previous versions a breaking change with
HtmlInput.setAttribute
was introduced.Currently, when changing
type
ofHtmlInput
a new instance is created and the instance worked on is no longer attached.Looks like this behavior is intended but causes undesired side effects as the user has absolutely no way knowing they are working on a stale object.
(
HtmlElementBuilder
is a helper class we created, it basically just creates aStringWebResponse
and passes it to toPageCreator
)Example 1 :
Which result in this result:
Another case:
Results in:
There are workarounds for this but this feels very error prone.
The text was updated successfully, but these errors were encountered: