Which version of the product are you running? I know we've addressed this issue in a variety of rollups in mid-March of this year. If you tell me the version, I can confirm if it's in a rollup.
One note - decause the fix occurs in the component "template" we use to generate components, the generators would have to be "re-ran" again to get the fix.