Fixed mastodon checkbox on new entry page
This commit is contained in:
@@ -1358,3 +1358,15 @@ The checkbox takes the full width of the grid which forces the label to be print
|
||||
|
||||
### Assistant outcome
|
||||
Fixed the actual layout conflict: `.form-section label` uses a grid layout whose selector overrode the tag label's flex layout. Added the more specific `.form-section label.tag-checkbox` inline-flex rule and reset its checkbox margin, keeping each checkbox directly left of its tag text. The focused API test module passed with 35 tests and `git diff --check` passed.
|
||||
|
||||
### User
|
||||
Only show the Mastodon publishing on new page if the user has Mastodon posting configured. Then default the checkbox to yes
|
||||
|
||||
### Assistant outcome
|
||||
Added a safe `configured` status to the authenticated Mastodon configuration response. New Entry now hides its Mastodon publishing section unless the current user has both an instance and access token configured; when shown, its checkbox defaults to checked. Link creation accepts `post_to_mastodon`, allowing an unchecked control to skip Mastodon while preserving dispatch of other plugins. Added posting and configuration regression coverage.
|
||||
|
||||
### User
|
||||
In the currently running contaier the user olaf has no mastodon configured but the mastodon checkbox is still visible
|
||||
|
||||
### Assistant outcome
|
||||
Found that `.form-section { display: grid; }` appeared later in the stylesheet than `.hidden { display: none; }`, overriding the initial hidden state of the Mastodon fieldset. Added `.form-section.hidden { display: none; }`, so the publishing control stays hidden until the authenticated configuration check explicitly reveals it.
|
||||
|
||||
Reference in New Issue
Block a user