Context Navigation

Changes between Version 1 and Version 2 of Ticket #32102, comment 5

v1	v2
2	2	Yep thats true, but not everyone wants/needs Emoji and/or wants the additional load of these inline Script and Style in his site. Installing a Plugin to remove something from WordPress isn't always the best solution.
3	3
4		Why isn't it possbile to add (or at least discuss) the {{{add_theme_support( 'emoji' );}}} or an option for this? I would understand, if you argue with the "Decisions not Options"-think, but in Backend you've also the option for {{{use_smiles}}} which ~~can be "easily " deactivated by ''another'' Plugin~~.
	4	Why isn't it possbile to add (or at least discuss) the {{{add_theme_support( 'emoji' );}}} or an option for this? I would understand, if you argue with the "Decisions not Options"-think, but in Backend you've also the option for {{{use_smiles}}} which should be removed and can be "easily" replaced by ''another'' Plugin to control this.
5	5	Additonal we have some "features" which are controlled by {{{add_theme_support()}}}. Seems like a big inconsistency for me, when which "rule" (option in backend, theme-support, decission from WP for everyone, ''something else'') is used.