Adding textInputFont and TextInputFontDefault properties to inputController was breaking many client who used to set the font straight to textInput font property.
The reason behind adding this property was to fully support dynamic types.
Reverting this change will break dynamic types support for textfields.
Pivotal issue to address the work needed to add this property: #156518577
* Extracting Accessibility out of FeatureHighlightViewController to a mutator.
Tests added.
Example updated.
* Revert "Extracting Accessibility out of FeatureHighlightViewController to a mutator."
This reverts commit 0b5433ebf86366087b240c4dc4992a0603fa73e0.
* Adding Font themer to TextFields.
* extra lf.
* dealing with warnings.
* Fixing unit tests.
* commenting out low priority set up for bounds
* commenting out tests to see if tests would fail.
* tests are back, scale could have been zero.
* temp fix in case the fonts are zero.
* check for default inside setter.
* fix compliing mistakes.
* add documentation for the change.
* Example of dynamic size with different fonts.
* added support for dynamic type with custom fonts.
* fixed the top overlapping issue
* Replied to comment and fixed the issues.
* Adding Text Input property to InputController
Changing the value of mdc_adjustsFontForContentSizeCategory should not effect the actual controller fonts that are set by user but only the properties of the actual textfield. In order to do that I moved the resizing of fonts away from the properties of InputController and into update layout.
* Fixing the comment. Changing font scheme to not accept nullable controllers.
* change documentation.
