id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
12120	Dynamic size restrictions in AutoGrow feature	Olek Nowodziński		"At the moment AutoGrow plugin supports [http://docs.ckeditor.com/#!/api/CKEDITOR.config-cfg-autoGrow_minHeight config.autoGrow_minHeight] and [http://docs.ckeditor.com/#!/api/CKEDITOR.config-cfg-autoGrow_maxHeight config.autoGrow_maxHeight] along with [http://docs.ckeditor.com/#!/api/CKEDITOR.editor-event-autogrow editor#autoGrow] event, which can be used to force a custom height on every editor resize, i.e.

{{{
CKEDITOR.replace( 'editor2', {
	extraPlugins: 'autogrow',
	autoGrow_maxHeight: 400,
	removePlugins: 'resize',
	on: {
		autoGrow: function( evt ) {
			evt.data.newHeight = 42;
		}
	}
} );
}}}

Such behaviour is desired when the space around the editor is changing, i.e. window is resized, other page elements collapse or expand.

The event, however, controls height only, while `overflow-y` of editable area remains relative to `config.autoGrow_maxHeight`. The result is that even though it is possible to customise the main behaviour of the plugin, the scrollbar of editable area might be missing, making editor contents unreachable, which is a serious UX flaw. 

Possible solutions:

1. Implement `editor.plugins.autoGrow.setMaxHeight`, which would override `config.autoGrow_maxHeight` on demand. 
 a. + Solves the problem.
 b. - Change is permanent. Some devs may want to override `autoGrow_maxHeight` on demand, while in other cases they would expect default configuration to be preserved and respected.
2. Re-implement editor#autoGrow event, so `autoGrow_maxHeight` can be changed for every single event.
 a. + Solves the problem.
 a. + The impact of `config.autoGrow_maxHeight` remains.
 b. - Makes the code less obvious.
 c. - It's not straightforward. Hard to reach in documentation."	New Feature	confirmed	Normal		General	4.0		Drupal	wim.leers@…