Overview - Ghost

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
30610
5c2496c5 Added the Keyboard shortcuts pane to the React editor's settings sidebar no ref The React post editor's settings sidebar had no reference list of the chords and slash commands the editor answers to, so a writer had to leave the editor to look one up. The rows are a pure data module rather than markup, so the platform glyphs are decided in one place and unit tested: Mac writers see the Mac symbols and everyone else the key names, read from the user agent through a shared helper that the app sidebar's search hint now reads too. The pane itself is the sidebar's existing subview shell, so it opens, closes and returns focus like the panes beside it, and every role that can open the panel can open it. A glyph standing in for a key name carries a tooltip naming it, which has to be a real tooltip rather than a title attribute: a key cap takes no pointer events of its own, so nothing can reach a native one.
by Steve Larson
S
Succeeded
30610
e6a4f60d Added the Keyboard shortcuts pane to the React editor's settings sidebar no ref The React post editor's settings sidebar had no reference list of the chords and slash commands the editor answers to, so a writer had to leave the editor to look one up. The rows are a pure data module rather than markup, so the platform glyphs are decided in one place and unit tested: Mac writers see the Mac symbols and everyone else the key names, read from the user agent through a shared helper that the app sidebar's search hint now reads too. The pane itself is the sidebar's existing subview shell, so it opens, closes and returns focus like the panes beside it, and every role that can open the panel can open it. A glyph standing in for a key name carries a tooltip naming it, which has to be a real tooltip rather than a title attribute: a key cap takes no pointer events of its own, so nothing can reach a native one.
by Steve Larson
S
Succeeded
30610
2cb647ef Added the Keyboard shortcuts pane to the React editor's settings sidebar no ref The React post editor's settings sidebar had no reference list of the chords and slash commands the editor answers to, so a writer had to leave the editor to look one up. The rows are a pure data module rather than markup, so the platform glyphs are decided in one place and unit tested: Mac writers see the Mac symbols and everyone else the key names, read from the user agent the way the rest of the React admin reads it. The pane itself is the sidebar's existing subview shell, so it opens, closes and returns focus like the panes beside it, and every role that can open the panel can open it.
by Steve Larson
S