-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Survey task: increase task area width to 540px for workflow with survey task #6237
Comments
@seanmiller26 - for a workflow with multiple steps, should the increased task area width apply to steps without a survey task or only to a step with a survey task? |
Yes, we should keep the task area a consistent size, if possible. |
@seanmiller26 - currently the subject viewer and task area layout goes from horizontal to vertical at 768px ( The Grommet ResponsiveContext |
Yes, this is something I'd like to explore with this task as a pathfinder for other task types. I think best to move forward with the initial styling in this issue. Then I can try it out on staging and I'll be able to make a more informed decision once I can play around with it. |
@mcbouslog there was recent discussion about unexpected changes to task area styling when going back and forth between task types in this Issue: #6271 (comment) Not caused by any changes to the survey task code, but I want to link it here in case it's worth considering better management of task area styling in general. |
Package
Choose from the list:
Is your feature request related to a problem? Please describe.
Allow more space for the task area and its components. In turn, this helps with #6210 when the task is a Survey.
Describe the solution you'd like
Increase the task area to be 540px. Figme for reference https://www.figma.com/design/ASqNlLhicNRzEDhYDA2t8j/Survey?node-id=65-1006&m=dev&t=PxDxXDB67AH8V9Aa-1
Specific margins and other annotations here:
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: