Prime example of a “feature*” IMO.
*consequence of an unintended interaction that wasn’t fully thought out but isn’t seen worth the time or effort to change
For the record, Webspinner has worked this way third trait was last changed. Previously, she would only deal triple skull damage to poisoned enemies, so this interaction never happened. A different troop, Crimson Arrow, that applies Hunter’s Mark on skull damage worked similarly since its introduction by dealing double skull damage on the turn it applied the Hunter’s Mark.
Yeah, it seems a bit silly, but it isn’t even remotely as overpowered or broken as implied.
I wouldn’t expect this to ever be fixed in a satisfactory manner, and if it does, it wont be soon. The most likely outcomes would be:
a) It remains how it is now
b) Webspinner is hard nerfed to not inflict web on skull damage
c) Webspinner is reverted to not deal triple damage to webbed troops and loses Arachnean Weaver synergy (the most likely reason this was even added)
This, combined with a previous “not a bug” reply from a dev shows that the current course of action is a. Comparatively few people would complain if it was truly fixed to only calc triple damage if web was already applied, but mostly people just don’t want to see b or c, which is historically what they would do. Hence, most readily accept that it is “not a bug”, because they know the consequences otherwise.