When in the editor, alter the "twocolumns" and "threecolumns" classes to have a subtle border

RESOLVED FIXED

Status

developer.mozilla.org
Editing
--
enhancement
RESOLVED FIXED
a year ago
a year ago

People

(Reporter: sheppy, Assigned: sheppy)

Tracking

({in-triage})

Details

(Assignee)

Description

a year ago
When editing, there are options to apply the classes "twocolumns" or "threecolumns" to the content, using the toolbar. These classes do the obvious: they create a <div> which displays its content in either two or three columns.

While editing, it is hard to see where these special blocks are, and to see where the columns are, especially if you have only a small amount of information displayed. It would be helpful to have a subtle border, perhaps a very light grey or pale blue, drawn around the borders of each column while in the editor.

We already have a custom version of the "hidden" class while editing, so this ought not to be difficult to do.
(Assignee)

Comment 1

a year ago
I've submitted a PR for this: https://github.com/mozilla/kuma/pull/4080

It adds a light blue border around the columns in both two and three column modes both on desktop and mobile when editing only.
Severity: normal → enhancement
Keywords: in-triage

Comment 2

a year ago
Commits pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/71a80ceade125cc4891e16f917f96187b9eafaaa
bug 1325097: Make columns more visible in editor

Updated the twocolumns and threecolumns classes so they draw with a pale
blue dotted border around the columns when in the editor, for ease of
layout work. The format is in a variable ($editor-box-border) so it can
be reused in other similar cases if needed.

https://github.com/mozilla/kuma/commit/136cd575cd68aa31a4ee0d052b154ff9f9fd2396
Merge pull request #4115 from jwhitlock/column_editor_1325097

bug 1325097: Make columns more visible in editor
Pushed to staging
Assignee: nobody → eshepherd
Fix pushed to production
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.