IMHO most must cases in the plugin submission checklist needs to be loosened and changed to should, because now, until UXP matures, it’s nearly impossible to normally achieve responsiveness and adaptiveness in the panel. Lots of at least a year old CSS is not supported at all…
- For panel plugins, no content should be clipped when the plugins panel is at minimum width.
- For panel plugins, the plugin’s UI content must adapt appropriately when the panel width is increased.
- For panel plugins, the plugin’s UI content must adapt appropriately when the panel width is decreased.
- The plugin must be functional when the host app application window is at maximum size.
- The plugin UI must scroll when all content is not visible on the screen.
- UI elements in the plugin must not overlap or truncate.
- UI content must wrap or adapt as necessary to accommodate the available width of the UI.
None of the
gap forms is supported (nor
text-overflow: ellipsis is not supported. When panel height is decreased, default scroll is not there. It’s simply inventing the wheel - you have to write custom media queries and lots of CSS for usually already for years supported features out of the box in all the browsers (including mobile; and yes, I know UXP is not a browser)
Currently I’m trying to make a panel with a row of buttons, which have icon and text. It’s as simple as it gets and usually it would take half an hour at most, but not with UXP. Spent at least a day and I’m still nowhere near finish. Resizing panel makes a mess and I’m so frustrated…
sp-action-button instead of the
button in this example
I could make two separate panels (row and column), but that would be just ridiculous and in no way it would satisfy the all musts of the panel. Especially the last bullet point - requirement is there, but no tools provided to achieve it…
Exact same HTML and CSS:
I would love if Adobe provided a sample plugin with a really fully adaptive UI