this is also the case in v2.0.0-beta.3

2016-10-19 10_52_54-Report Issue - MantisBT.png (8,415 bytes)   

2016-10-19 10_52_54-Report Issue - MantisBT.png (8,415 bytes)   

This is the css that was used in v1.3

div.form-container fieldset label.required:before,
th label.required:before,
td label.required:before {
    font-size: 8pt;
    content: '* ';
    color: red;
}

should we apply something like that, instead of explicitly printing the *?

should we apply something like that, instead of explicitly printing the *?

IMO, yes, that would be much better

EDIT: maybe consider using a margin-right for the spacing instead of hardcoded space (and we should make sure it works with RTL as well)

@dregad @cproensa
Are you aware of css/common_config.php which deals with required class?

div.form-container fieldset.required:after {
    position: absolute;
    margin: -1.75em 0em 0em .5em;
    font-size: 8pt;
    content: '* <?php echo lang_get( 'required' ); ?>';
    color: red;
}

This approach allows to implement also language dependant display (Assuming that * is not the best characater e.g, for Chinese).
But I thought also about removing this generated CSS as it's not cached in browser and generated / delivered again and again.
Maybe delivering static content and having something like lang/css/english.css lang/css/german.css ...

Another thing to consider would be Translatewiki.

[Edit 1] And while we are on it, we should also consider HTML5 client side validation, https://www.w3schools.com/tags/tryit.asp?filename=tryhtml5_input_required

https://github.com/mantisbt/mantisbt/pull/1026

[Edit 2] The HTML5 required attribute could also be used for styling https://css-tricks.com/almanac/selectors/r/required/

@atrol This CSS was used to display the "legend" for the asterisk marking mandatory fields, at the form's bottom in Mantis 1.3. As far as I can tell, it is no longer used in 2.0 (git grep 'fieldset.*class' yields no results in php files), so the style could probably be removed.

Note: an alternative to the dynamic stylesheet could be to use a jQuery AJAX to get the language string, which would probably be easier than maintaining many language-specific static CSS files.

Re: client side validation, required only checks that the field is effectively not empty; a single space bypasses that. But anyway using this attribute makes perfect sense.

Ideally, with PR 1026, required inputs would be identified by it's "required" property.

If we still want to add a "*" to labels, we could base the display of that on the related input's property.
Afaik, this can't be done directly in css, when having
<label for="xxx"></label> <input id="xxx">

However, if having a label.required style, this class can be added with js to those labels linked to required inputs.
(Or simply use it staticly on the label)

As far as I can tell, it is no longer used in 2.0

Right, didn't find any usage, opened 0023310 to remove it.