Overview - Ghost

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
30608
2c568e28 Added the Code injection pane to the React editor's settings sidebar no ref The post settings sidebar was missing the header and footer code a single post injects into the page it renders on, so a writer had to go back to the Ember editor to set it. The pane reuses Shade's CodeEditor with the HTML grammar the rest of Admin loads for code injection, so the two editors behave the way Settings and tag detail already do. Both fields are ordinary settings fields: staged as the writer types and committed on the blur that ends the edit, which leaves the save policy to decide whether a draft persists them or a published post holds them until Update. Every role that can open the panel gets the pane. The pane listens for Escape on the window, and CodeMirror leaves an Escape no binding answers unprevented, so the pane closed out from under a writer typing in an editor and its Tab stayed trapped in the code. A lowest-precedence Escape binding on these two editors arms CodeMirror's own tab-focus mode and consumes the event, so a completion list or a wide selection still answers Escape first, the pane stays open, and the next Tab moves to the footer editor and on out of the pane.
by Steve Larson
S
Succeeded
30608
2c568e28 Added the Code injection pane to the React editor's settings sidebar no ref The post settings sidebar was missing the header and footer code a single post injects into the page it renders on, so a writer had to go back to the Ember editor to set it. The pane reuses Shade's CodeEditor with the HTML grammar the rest of Admin loads for code injection, so the two editors behave the way Settings and tag detail already do. Both fields are ordinary settings fields: staged as the writer types and committed on the blur that ends the edit, which leaves the save policy to decide whether a draft persists them or a published post holds them until Update. Every role that can open the panel gets the pane. The pane listens for Escape on the window, and CodeMirror leaves an Escape no binding answers unprevented, so the pane closed out from under a writer typing in an editor and its Tab stayed trapped in the code. A lowest-precedence Escape binding on these two editors arms CodeMirror's own tab-focus mode and consumes the event, so a completion list or a wide selection still answers Escape first, the pane stays open, and the next Tab moves to the footer editor and on out of the pane.
by Steve Larson
S
Succeeded
30608
3e49237b Added the Code injection pane to the React editor's settings sidebar no ref The post settings sidebar was missing the header and footer code a single post injects into the page it renders on, so a writer had to go back to the Ember editor to set it. The pane reuses Shade's CodeEditor with the HTML grammar the rest of Admin loads for code injection, so the two editors behave the way Settings and tag detail already do. Both fields are ordinary settings fields: staged as the writer types and committed on the blur that ends the edit, which leaves the save policy to decide whether a draft persists them or a published post holds them until Update. Every role that can open the panel gets the pane. The pane listens for Escape on the window, and CodeMirror leaves an Escape no binding answers unprevented, so the pane closed out from under a writer typing in an editor and its Tab stayed trapped in the code. A lowest-precedence Escape binding on these two editors arms CodeMirror's own tab-focus mode and consumes the event, so a completion list or a wide selection still answers Escape first, the pane stays open, and the next Tab moves to the footer editor and on out of the pane.
by Steve Larson
S
Succeeded
30608
d3411e9f Added the Code injection pane to the React editor's settings sidebar no ref The post settings sidebar was missing the header and footer code a single post injects into the page it renders on, so a writer had to go back to the Ember editor to set it. The pane reuses Shade's CodeEditor with the HTML grammar the rest of Admin loads for code injection, so the two editors behave the way Settings and tag detail already do. Both fields are ordinary settings fields: staged as the writer types and committed on the blur that ends the edit, which leaves the save policy to decide whether a draft persists them or a published post holds them until Update. Every role that can open the panel gets the pane.
by Steve Larson
S