> Because the fallback is dependent on the widget

I think it's more accurate to say "the fallback is dependent on whether or not the item is a jeditable field", which is a permutation that is managed by the macro without any intervention by the widget. So I think having the fallback centralized in `oae.components.css` is valid.

It seems it's just the field width that is something that will be different in a lot of cases. My feeling is that it's not worth to decentralize the whole IE9 workaround just to fiddle the width. I suggest that we leave these 1-liners as-is and remove them (along with the rest in `oae.components.css`) when IE9 is no longer supported.