[MGNLFORM-122] Align layout of formPassword with the other field layout Created: 12/Mar/12  Updated: 24/May/12  Resolved: 14/May/12

Status: Closed
Project: Magnolia Form Module
Component/s: None
Affects Version/s: 1.4.1
Fix Version/s: 1.4.2

Type: Bug Priority: Minor
Reporter: Samuel Schmitt Assignee: Milan Divilek
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File formPassword.patch    
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

The output HTML of formPassword.ftl differs form the other fields. It's really annoying when you design the form, you need to create a special CSS for the password or extends it and provide a better ftl.

The problem is that the <label> wraps the span AND the input which is not the case for the other fields.

Output of the password field:

        <label id="dsd_label" class="" for="dsd">
            <span>
            Password
            </span>
        <input name="dsd" id="dsd" value="" type="password">
      </label>

Output of another field:

        <label for="email">
            <span>
            Your Email
                <dfn title="required">*</dfn>
            </span>
        </label>
        <input name="email" id="email" value="" maxlength="50" type="text">



 Comments   
Comment by Will Scheidegger [ 07/May/12 ]

This patch makes formPassword.ftl behave like formEdit.ftl

Comment by Jan Haderka [ 10/May/12 ]

Increasing priority to make sure this gets fixed (should be quick and easy). Please reset to Minor when resolving the issue.

Comment by Milan Divilek [ 14/May/12 ]

Commit message.

Generated at Mon Feb 12 05:37:05 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.