People often click the “Settings” link when they see “HTML list | Settings” which causes them to miss how to change the main formatter settings. This came up during the BADCamp 2012 usability study, in essence people :

  • Accidentally click the wrong one, to change either the kind of list and or adjust its configuration (settings)
  • Are surprised to find settings after clicking Apply (the first time configuration

Having examined the different screens this occurs caching, pager, menu, acces, format etc. I have found that most of them use this only to capture a small set of settings, thus gaining very little in terms of vertical real estate that is needed to capture all of the settings. Only some of menu, and some of (exposed format) would benefit from this pattern. But even then I think the time that all of our users lose on accidentally clicking the wrong one, is a huge gain on the lost vertical experience of minimal scrolling.

I suggest wherever possible we merge the two settings, using states to disclose the right kind of settings.

Files: 
CommentFileSizeAuthor
#19 vdc-1836440-19.patch11.09 KBdawehner
FAILED: [[SimpleTest]]: [MySQL] 59,243 pass(es), 9 fail(s), and 0 exception(s). View
#14 drupal-1836440-14.patch10.91 KBdawehner
FAILED: [[SimpleTest]]: [MySQL] 57,990 pass(es), 9 fail(s), and 0 exception(s). View
#14 interdiff.txt868 bytesdawehner
#12 drupal-1836440-12.patch10.83 KBdawehner
PASSED: [[SimpleTest]]: [MySQL] 55,883 pass(es). View
#5 drupal-1836440-5.patch10.8 KBdawehner
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch drupal-1836440-5.patch. Unable to apply patch. See the log in the details link for more information. View
#3 test.png22.91 KBdawehner
#3 test1.png34.57 KBdawehner
#3 drupal-1836440-3.patch7.04 KBdawehner
FAILED: [[SimpleTest]]: [MySQL] 54,656 pass(es), 35 fail(s), and 2 exception(s). View
#1 which-of-these-two-do-I-need.png192.98 KBBojhan

Comments

Bojhan’s picture

Priority: Normal » Major
FileSize
192.98 KB

Updated the summary, also raising criticality. Primarily because this small usability issue, has a large cumulative cost in time that people spend accidentally in the wrong place. Also given that I'd like to see this fixed as part of D8.

I have updated the summary.

Bojhan’s picture

Issue summary: View changes

Updated issue summary.

dawehner’s picture

Assigned: Unassigned » dawehner

I will start with converting the style settings, and just see how this goes.

dawehner’s picture

Status: Active » Needs review
FileSize
7.04 KB
FAILED: [[SimpleTest]]: [MySQL] 54,656 pass(es), 35 fail(s), and 2 exception(s). View
34.57 KB
22.91 KB

That's just a start, but submitting values does work.
test.png

test1.png

Status: Needs review » Needs work

The last submitted patch, drupal-1836440-3.patch, failed testing.

dawehner’s picture

Status: Needs work » Needs review
FileSize
10.8 KB
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch drupal-1836440-5.patch. Unable to apply patch. See the log in the details link for more information. View

Just fixing the tests, so this should be at least green.

One thing which would be cool in this issue or maybe a follow up: use ajax reload the available settings for a style/row.

Bojhan’s picture

Title: Changing format settings under "HTML list| Settings" is unclear » Changing format settings under "HTML list | Settings" is unclear
Assigned: dawehner » Unassigned
Issue tags: +sprint

No idea, this wasn't showing in any of my trackers. Added it to my blog post, and definitely worthwhile to persue the AJAX reloading without it its quite confusing

Bojhan’s picture

Title: Changing format settings under "HTML list | Settings" is unclear » The distinction between the two items "HTML list | Settings" is unclear
dawehner’s picture

Issue tags: +Needs manual testing

.

yoroy’s picture

Issue tags: -usabiity +Usability

because of a typo in the 'usability' tag :)

dawehner’s picture

#5: drupal-1836440-5.patch queued for re-testing.

Status: Needs review » Needs work
Issue tags: +Usability, +Needs manual testing, +d8ux, +sprint, +VDC, +BADCamp2012UX

The last submitted patch, drupal-1836440-5.patch, failed testing.

dawehner’s picture

Status: Needs work » Needs review
FileSize
10.83 KB
PASSED: [[SimpleTest]]: [MySQL] 55,883 pass(es). View

Rerole.

Would be cool to have people playing around with it.

damiankloip’s picture

The patch works well enough in it's current form. We need to add ajax updating of the options part of the form though. So this mimics behaviour we already have for exposed form checkbox and single/grouped filter radios.

dawehner’s picture

FileSize
868 bytes
10.91 KB
FAILED: [[SimpleTest]]: [MySQL] 57,990 pass(es), 9 fail(s), and 0 exception(s). View

That's just a start.

aiypz’s picture

Had a play around with the patch and this feels much clearer. As damianKloip says the ajax part to update the options will be important as a user could easily change some options for one format and then decide to change the actual format which will really confuse them when they then apply it.

yoroy’s picture

#14: drupal-1836440-14.patch queued for re-testing.

Status: Needs review » Needs work
Issue tags: +Usability, +Needs manual testing, +d8ux, +sprint, +VDC, +BADCamp2012UX

The last submitted patch, drupal-1836440-14.patch, failed testing.

Bojhan’s picture

This is really great, could this get some more work? This is one of the few major Views UI issues.

dawehner’s picture

Status: Needs work » Needs review
FileSize
11.09 KB
FAILED: [[SimpleTest]]: [MySQL] 59,243 pass(es), 9 fail(s), and 0 exception(s). View

Just a rerole.

Status: Needs review » Needs work

The last submitted patch, vdc-1836440-19.patch, failed testing.

Bojhan’s picture

It looks like it failing on the same thing as before

Bojhan’s picture

Issue summary: View changes

updatin

tim.plunkett’s picture

Priority: Major » Normal
Issue summary: View changes
Issue tags: +Needs issue summary update

This needs a proper issue summary. It's not clear why this is major, nor how the patch attempts to address the issue.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.