Why does a widget have a theme association and what triggers that association?

You can copy widgets and target them purely at a single theme, then it would have a theme value in the xml header when exported/imported

I have seen instances in the past where they have been created but not known the cause so would be interested to see what other feedback comes in for this

If there were erroneous I have previously just deleted them

Karl Barber said:

You can copy widgets and target them purely at a single theme, then it would have a theme value in the xml header when exported/imported

Yes, we have seen this, where you can go in one-by-one and copy a widget and you are prompted to target a theme

Karl Barber said:

I have seen instances in the past where they have been created but not known the cause so would be interested to see what other feedback comes in for this

This is more of what we're looking to identify the cause, specifically when

• All of a sudden multiple widgets (10+, 20+) are suddenly "Theme:Social"
• If Themes are exported, then imported and the widgets get this association

Karl Barber said:

here were erroneous I have previously just deleted them

Yes, only challenge here is there is no way through visual studio to compare an out-of-the-box widget with the same widget Theme:Social, so you have to export them both, do a quick diff, then yes, I'd feel comfortable deleting it. 

It would be good to get some feedback from the product team as to why these theme targeted versions get created as I thought they would only be created if the xml contained the theme value