The docs say that resize accepts width and height as numeric pixel values or string CSS units, but I find that height can't be altered with a CSS string. This is easily demonstrated on your demo page. Open that page, open a JS console and enter this:
CKEDITOR.instances.editor1.resize('100%', '200px')
notice that nothing happens. Now try this:
CKEDITOR.instances.editor1.resize('100%', 200)
and it resizes as it should.
I'm seeing this in 4.4.1 as well as 4.4.3, though I'm stuck on 4.4.1 as I still can't make later versions work for me at all.
I'm not sure I fully
I'm not sure I fully understand... The docs state that
The new height. It can be an integer denoting a value in pixels or a CSS size value with unit.
So you either use an integer without a value for pixels or any other CSS-defined value which is not in pixels, with a unit?
Documentation Manager, CKSource
See CKEditor 5 docs, CKEditor 4 docs, CKEditor 3 docs, CKFinder 3 docs, CKFinder 2 docs for help.
Visit the new CKEditor SDK for samples showcasing editor features to try out and download!
Pixels are a valid CSS unit,
Pixels are a valid CSS unit, probably the most common one there is. The docs imply that 200 and "200px" should both work. A plain integer is unitless, so it needs to default to something, but that doesn't have any particular bearing on whether some specific "CSS size value with unit" (which is exactly what "200px" is) should not be allowed.
Further experiments lead me
Further experiments lead me to suspect that using a string for height does not work at all. None of these work, and they are all valid CSS values with units:
CKEDITOR.instances.editor1.resize('100%', '20em')
CKEDITOR.instances.editor1.resize('100%', '20rem')
CKEDITOR.instances.editor1.resize('100%', '5cm')
CKEDITOR.instances.editor1.resize('100%', '150mm')
I did find that this works:
CKEDITOR.instances.editor1.resize('100%', '150')
So numbers (whether as strings or ints) work ok, CSS values don't.
I do believe it's related to
I do believe it's related to this issue... So it's been reported. There's a good chance it will be fixed eventually since IBM reported it.
Customer and Community Manager, CKSource
Follow us on: Facebook, Twitter, LinkedIn
If you think you found a bug in CKEditor, read this!