Alternative solution :

<div class="col-xs-12 col-sm-2 answer-item radio-item col-md-1 radio">
<input type="radio" onclick="checkconditions(this.value, this.name, this.type)" value="1" id="answer89495X13X671" name="89495X13X67" class="radio">
<label id="label-answer89495X13X671" class="label-text label-clickable">
1 </label>
</div>

Then : we don't need any JS : label is activated.

Because : by default : answer/subquestion part don't have HTML editor. User can broke HTML validator, but in great majority answer/subquestoion are really inlined.

Must discuss at dev meeting.

Alteranet 2:
<label class="col-xs-12 col-sm-2 answer-item radio-item col-md-1 radio">
<input type="radio" onclick="checkconditions(this.value, this.name, this.type)" value="1" id="answer89495X13X671" name="89495X13X67" class="radio">
<span id="label-answer89495X13X671" class="label-text label-clickable awesome-label">
1 </span>
</label>

Did you test this locally?

One alternative solution ?
http://testing.sondages.pro/masterall/

Didn't test : because awesome-bootstrap-checkbox is a template issue : not a core issue.

You mean : did i test one of the solution ?

Yes, did you try your solution? :)

I propose 3 fix, and actually : all HTML part is redone 3/4 times a week.
I don't fix whole HTML if this is brolken again 1 week after

I vote for
<label class="col-xs-12 col-sm-2 answer-item radio-item col-md-1">
<input type="radio" onclick="checkconditions(this.value, this.name, this.type)" value="1" id="answer89495X13X671" name="89495X13X67" class="radio">
<span id="label-answer89495X13X671" class="label-text label-clickable awesome-label">
1 </span>
</label>

Can broken HTML validity : div inside span : but more clean for majority.

Broken HTML is worst than empty label.

I'm not sure here ....

And broken HTML happen only in few case. And more with a lot of user we have surely some user who put

< strong>< p>Text

And it break HTML validator but not HTML.

I think it's best to use n

1 : <div class="radio-item"><input type="radio"><label>The label</label></div>
2 : <label class="radio-item"><input type="radio"><span class="radio-label">The label</span></label>

With 1 : no need to update awesome-bootstrap-checkbox
With 2 : need to update/fix awesome-bootstrap-checkbox but can be in a pull request of awesome-bootstrap-checkbox

Denis: you're the one who first complained about the input being inside the label. Now that we've put out the input outside the label, you're complaining and ask to put back the input inside the label. At the same time, you're complaining that we change the HTML all the time....

You're also the one who pointed out that users could insert div, paragraph, tables, iframes, flash animatiosn, pictures, or anything else as label text. That's why I remove the label text from the label to an external div, linking this external div to the input with aria-labelledby, as you suggested. Now, you're asking to undo that work you asked for, and complain that we change the HTML all the time...

I agree I'd prefer not to have the empty label. As far as I know, it's not making any problem. Meanwhile, putting back the label text inside the label will make HTML validation problem. Google form is not using any label at all (nor any visible input), they're using only div and hidden input. IMHO, it's because they also went through all that debate.

Hi,

I never say : put an empty label.

You ask me solution by IRC at me only (why not discuss really of HTML flow at a dev metting ? Why not make some wiki pâge before ? Why not put a dev mantis and give the link to all dev ... etc ...).

I inform some user can add div inside subquestion, and that can broke HTML validator: this must be thinking but the way to fix it is unsure.

You want 3rd solution :
div class wrapper
input
div class label

Then OK, but i never make any decision on this whole HTML update ... It's exactly what i mean : if you want to fix HTML flow really, then do it with the cleanest way , and spoke to some user/dev before ...

You asked for all the other things you're now asking to remove, and you asked for them include in the bug tracker. Like here:
https://bugs.limesurvey.org/view.php?id=10530#c35967

Where your asking for the exact contrary that you're asking here (but already complain that the HTML changes all the time).

The label is necessary for Awesome Bootstrap Checkboxes.
The text label can contain block elements, breaking HTML validity if inside a label element.

An empty label doesn't make any problem. So, why do you want to remove it?

Yes:
Question : personnaly : i prefer:
label
text-node
/label
input

OR
input
label
text-node
/label

You see a text-node inside label ....

You add an empty label just for Awesome Bootstrap Checkboxes: NO other vreason ... don't tell me i ask an empty label .....

I think add an empty "anything" jsut for a css (who can be updated) don't make flexible, durable, and sustainable HTML

but do you see any actual problem, do you see any bug?
because putting back the label text inside the label makes bugs, we know it.
Removing the empty label would be the right solution.

We should directly speak with the ABC team to ask them to do it. They yet did it by the past:
https://github.com/flatlogic/awesome-bootstrap-checkbox/issues/17

I don't know why this feature were lost in the last versions.

Move to feature request : OK, not a bug a request :)

The user can vote ;)

still: if you find that the empty label is making any bug or problem, we'll remove it.