Page MenuHomePhabricator

Split long lists of checkboxes into 2 columns on forms
AbandonedPublic

Authored by chad on Mar 31 2015, 6:06 PM.
Tags
None
Referenced Files
F13207264: D12220.diff
Wed, May 15, 10:05 PM
F13192216: D12220.diff
Sun, May 12, 6:20 AM
F13190168: D12220.id.diff
Sat, May 11, 8:00 AM
F13173924: D12220.diff
Tue, May 7, 9:28 PM
Unknown Object (File)
Sat, May 4, 7:05 AM
Unknown Object (File)
Tue, Apr 23, 5:16 PM
Unknown Object (File)
Apr 19 2024, 4:52 PM
Unknown Object (File)
Apr 15 2024, 5:26 PM
Subscribers
Tokens
"Like" token, awarded by johnny-bit.

Details

Summary

Mostly for discussion, but seems like an improvement. This breaks up long lines of checkboxes on forms into two uniform columns when 6 or more items exist,

Test Plan

In practice, I could only find Maniphest and Advanced Search saw layout improvements. Tested new forms still work.

Screen_Shot_2015-03-31_at_11.04.06_AM.png (1×1 px, 133 KB)

Screen_Shot_2015-03-31_at_11.04.16_AM.png (1×1 px, 224 KB)

pasted_file (731×320 px, 78 KB)

Diff Detail

Repository
rP Phabricator
Branch
aphont-checkbox
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 5054
Build 5072: [Placeholder Plan] Wait for 30 Seconds

Event Timeline

chad retitled this revision from to Split long lists of checkboxes into 2 columns on forms.
chad updated this object.
chad edited the test plan for this revision. (Show Details)
chad added reviewers: epriestley, btrahan.
chad edited the test plan for this revision. (Show Details)

We could also consider making these typeaheads now that we have "Browse". Not totally sure how I feel about that, but it doesn't seem wholly unreasonable.

Hmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm

Imma do some shots and think about it.

We could wait a bit and see how we feel about "Browse" in general. Not sure if it's actually useful or strictly an onboarding/new-user feature.

/ we-don't-have-subprojects-yet-so-we-have-hundreds-of-projects-with-the-same-name-prefix

We should definitely do that for "Document Types" at least, and it's probably fine for Maniphest Status/Priority as well.