Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split screen editing of widgets on a blog page shows TinyMCE too narrow #178

Open
robbieaverill opened this issue Apr 30, 2019 · 5 comments

Comments

@robbieaverill
Copy link
Contributor

CWP 2.3.x-dev

I'm not sure how to resolve this really.

image

@NightJar
Copy link
Contributor

NightJar commented May 2, 2019

🤔 Should the widgets not be in their own tab?
Seems that it's not just the TinyMCE that's too narrow, it's the same size as the Title field above it (which is expected). The whole EditForm is too narrow - the labels could be fixed by using .stacked class on the .form-group (iirc), but I think ideally the widgets should be on a separate tab (I'm sure they used to be, I've not looked at this module in some time though, so can't say for sure if that should still be the case).

@robbieaverill
Copy link
Contributor Author

They are in their own tab, but since it's two columns it's not really designed for this kind of viewport

@NightJar
Copy link
Contributor

NightJar commented May 2, 2019

Oh sorry, you're looking at the widgets tab, where one of the widgets is a content area powered by TinyMCE 😅

I guess a possible solution would be similar to how elemental (4 - inline editing) is managed by an accordion style 'content drawer' containing the form...

One could probably then start questioning the ongoing support for the widgets module at that point though... 🤔
The two modules are very similar, and although they do fill slightly similar use cases I think an argument could be made for adapting the interface of one for the other... etc.

@robbieaverill
Copy link
Contributor Author

@scott1702 I think you worked out this UI most recently - do you have any thoughts?

@robbieaverill
Copy link
Contributor Author

The opposite of this happens on CWP 1.9.3:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants