Opened 12 months ago

Last modified 5 months ago

#2750 new defect

"WebApp Configuration" Need UX Attention

Reported by: anonymous maybe Owned by: sadie
Priority: minor Milestone: undecided
Component: apps/console Version: 0.9.46
Keywords: Cc:
Parent Tickets: Sensitive: no



and try to untick "Run as Startup" then press on "Stop" then the tick mark will backed to "Run as Startup" field which then user needs to untick it again before pressing "Save WebApp? Configuration"

Service (Wrapper) Logs

I2P version:	0.9.46-0-1ubuntu1
Java version:	Debian 11.0.7 (OpenJDK Runtime Environment 11.0.7+10-post-Debian-3deb10u1)
Wrapper version:	3.5.30
Server version:	9.4.15.v20190215
Servlet version:	Jasper JSP 2.3 Engine
JSTL version:	standard-taglib 1.2.5
Platform:	Linux amd64 4.19.125-1.pvops.qubes.x86_64
Processor:	Haswell Core i3/i5/i7 model 60 (coreihwl)
JBigI status:	Locally optimized library loaded from file
GMP version:	6.1.2
JBigI version:	4
JCpuId version:	3
Encoding:	UTF-8
Charset:	UTF-8
Built By:	Undefined


Change History (4)

comment:1 Changed 12 months ago by zzz

Right, that's the way it works. You didn't click 'save' the first time. What's your suggestion? That 'stop' also does 'save'?

comment:2 Changed 12 months ago by anonymous maybe

yes exactly

comment:3 Changed 10 months ago by zzz

Disagree with the proposal, I don't think it's good UI design, or particularly easy to implement, but will await guidance from sadie.

comment:4 Changed 5 months ago by sadie

Is the workflow to actually configure an app to NOT start on start up to
: uncheck it, stop it and save it?

When I tested this, and unclicked an app to run at start up and then saved the web app config option it appears that I have accomplished the task and the app remains unchecked.

I find that the option to *stop* is confusing in the the workflow.

Note: See TracTickets for help on using tickets.