Problem/Motivation
Right now width and height are intentionally text fields. Previously I've shunned only pixel integer width/height attributes (#2602124: Make video player responsive by default, hide not applicable width/height options) because they screwed up my ability to do responsive. Now that this is supported natively, is this a problem still?
Would someone conceivably care about using values like "50%" or "50em"? Making these pixels could clarify the UI a fair bit.
Proposed resolution
Make them pixels only.
Remaining tasks
Decide and patch.
User interface changes
Extra field suffix and description in the formatter settings.
API changes
Inability to do non-pixel units.
Data model changes
Change from a string to an integer in formatter settings.
Comments
Comment #2
sam152 commentedComment #3
sam152 commentedComment #7
sam152 commentedComment #9
sam152 commentedI think because the values can still be set programatically in exceptional circumstances, this is fine for the 90% case.
Comment #11
sam152 commented