You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been told that there is no current option in core to put theme settings anyplace other than this one column.
Proposed solution
I would like the option to place a theme setting above or below the page preview such that it can stretch the full width of the page OR the ability to add another tab or another settings page to a theme.
I've been told that this is currently not possible.
Alternatives that have been considered
Additional information
I know that this problem has been discussed in the past. I went looking for an existing issue, but could not find one. I was inspired by this request in the CSS Editor issue queue.
Agree, this needs to be full width. In addition to that i'd even suggest getting the full box as some sort of modal popup on the frontend (e.g. from the side, like an inline iFrame?) For more fluidity.
Description of the need
If a theme uses the Color module, all settings are forced into the left column while the preview for the color module takes up 2/3 of the page.
We have situations in which this is very cramped and unpractical. See: backdrop-contrib/css_editor#6
Or see the CSS options in Tatsu:
backdrop-contrib/tatsu#72
I've been told that there is no current option in core to put theme settings anyplace other than this one column.
Proposed solution
I would like the option to place a theme setting above or below the page preview such that it can stretch the full width of the page OR the ability to add another tab or another settings page to a theme.
I've been told that this is currently not possible.
Alternatives that have been considered
Additional information
I know that this problem has been discussed in the past. I went looking for an existing issue, but could not find one. I was inspired by this request in the CSS Editor issue queue.
backdrop-contrib/css_editor#6
The text was updated successfully, but these errors were encountered: