The lack of proper tooling or framework is no excuse for misusing technology or taking shortcuts. Don't get me wrong, I don't think that is the case here, I am merely exaggerating for the sake of argument. Nobody gets hurt when placing an input inside a label :)
As for your assessment on the proper semantic solution I agree with your concept, but that hardly is relevant. We are talking about semantic HTML that allows for meaning and flexibility for a practical purpose. What is semantic in HTML and in our minds can differ greatly, unfortunately.
Therefore, personally I tend to opt for the most semantic and common way of doing things, unless I have a good reason to deviate from it. Not wanting to include an id attribute is a pretty poor excuse IMHO to deviate from a common "standard", especially given potential downsides (which indeed are tiny here).
No harm is done and we are discussing mostly theories here, but if a tiny time saver wins from semantic correctness, where does it end? By that reasoning we dont have to document code, test it or do anything properly according to standards and conventions.
The lack of proper tooling or framework is no excuse for misusing technology or taking shortcuts. Don't get me wrong, I don't think that is the case here, I am merely exaggerating for the sake of argument. Nobody gets hurt when placing an input inside a label :)
As for your assessment on the proper semantic solution I agree with your concept, but that hardly is relevant. We are talking about semantic HTML that allows for meaning and flexibility for a practical purpose. What is semantic in HTML and in our minds can differ greatly, unfortunately.
Therefore, personally I tend to opt for the most semantic and common way of doing things, unless I have a good reason to deviate from it. Not wanting to include an id attribute is a pretty poor excuse IMHO to deviate from a common "standard", especially given potential downsides (which indeed are tiny here).
No harm is done and we are discussing mostly theories here, but if a tiny time saver wins from semantic correctness, where does it end? By that reasoning we dont have to document code, test it or do anything properly according to standards and conventions.