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
Current behavior if one attempts to clear the Template URL field is that the Save button is grayed-out and user cannot clear the field. This can lead to user's inability to resolve constant error in Portainer if the Template URL points to a malformed JSON file. Per #4865 this is apparently expected and desired behavior 🤯
If Portainer is going to disallow the Template URL field being blank, then it should insert the default URL into the field if the user attempts to blank the field, rather than grey-out the Save button and leave the user confused that they can't blank the field or make any changes to any items on the Settings page.
With the current behavior, the user cannot know that the field cannot be blanked and they can't inherently know the default URL so the user experience is indistinguishable from a bug [insert philosophical thought experiment about trees falling in the woods here].
This discussion was converted from issue #4898 on July 27, 2023 04:32.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Current behavior if one attempts to clear the Template URL field is that the
Savebutton is grayed-out and user cannot clear the field. This can lead to user's inability to resolve constant error in Portainer if the Template URL points to a malformed JSON file. Per #4865 this is apparently expected and desired behavior 🤯If Portainer is going to disallow the Template URL field being blank, then it should insert the default URL into the field if the user attempts to blank the field, rather than grey-out the
Savebutton and leave the user confused that they can't blank the field or make any changes to any items on the Settings page.With the current behavior, the user cannot know that the field cannot be blanked and they can't inherently know the default URL so the user experience is indistinguishable from a bug [insert philosophical thought experiment about trees falling in the woods here].
Thanks for your consideration !
Beta Was this translation helpful? Give feedback.
All reactions