The highest-ranked problems by far were related to CSS design debugging–studying that the main cause of puzzles like undesirable scrollbars and unexpected dimensions and position. Accordingly, my greatest priority at the moment is digging deeper into CSS debugging issues with further research and experiments. (You can assist by carrying my short fresh CSS Debugging follow-up survey! More information below.)

The Approaches


In terms of the browser problems card sort, we hear you loud and clear about the problem of”Moving CSS changes back into my editor.” We’re now in the process of adding export alternatives to our Changes panel, and would love your input our designs! DOM breakpoints are in the plans for this season.
We plan to continue enhancing our Access Panel; nonetheless, for today we will step back a little from our successfully launched Flexbox and Grid tools. Letting them amassing more real-world comments will permit us to swing back with fresh ideas afterwards.
Thank you!

You can view the entire MaxDiff and card sort rankings in this report.

# times rated finest – # instances rated worst
———————————-
# instances thing appeared

With guidance from Mozilla’s information scientists, I picked the MaxDiff method for the challenge-ranking portion of the survey. MaxDiff demands trade-offs to be made by the survey taker in subsets of this pool of options. This works nicely for ranking a number of options, which would be too overpowering for a card type. It generates a much more precise overall ranking by emphasizing relative differences.
Please have a minute with our fast single-page CSS Layout Debugging poll and assist us position the most time-consuming bugs. Your feedback will be tremendously helpful in clarifying our plans in beyond and 2019.

We need your help! The main takeaway from the very first survey was that designers and programmers of each experience level want to better understand CSS problems like sizing and abrupt scrollbars. We have started exploring and prototyping for exploring specific types of CSS bugs, potential tool ideas, but we want your feedback to guide our work.
The next part of the poll focused on particular frustrations with browser programmer tools. With this section we only offered 7 options, so we used a simple drag-and-drop card type.
The article Web Design Survey Findings and Next Steps appeared first on Mozilla Hacks – that the Web programmer blog.
Victoria & the Firefox DevTools group
In NovemberI wrote about my team’s work on experimental new website design tools. We conducted a survey to rank the challenges of internet design and development. A large thank you to everybody who participated in our layout procedure that is open! We received over 900 responses in 1 month, and discovered findings that continue to inform the Firefox DevTools’ 2019 roadmap.
We are exploring ways to lessen the pain of browser gaps, including auditing, tips, and a robust responsive design instrument.
In training, this produced 10 survey pages which each showed a set of 4 options in the pool of 23 total net design difficulties. Participants had to choose the”least” and”most” impactful options in each set. The ranking was subsequently determined by scores calculated with the following formula:

I suspect my old fashioned aisle here–WYSIWYG (“what you see is exactly what you get”)–brought to mind less-delightful adventures of yesteryear. There are clearly ways to improve developers’ lives with tools.