Bug or syntax problem: 5.1 B5 PC (5.1.0.0895) Warning when compiling new text input box
When I compile a document using the text input box syntax: {{ input id=QUESTION_1 | type=text | lines=3 | prompt=“Type Answer Here” }}
I get a warning: [Warning] Unexpected attribute on element <input>: type
Comments
-
Hi Tim
Just make id = Id
i.e. {{input Id=QUESTION_1 | type=text | lines=3 | prompt=“Type Answer Here”}}
Dave
===Windows 11 & Android 13
0 -
If that is indeed the workaround, then it's problematic that the PB compiler isn't case insensitive on the word "id".
I haven't tried this out myself. No time right now.
0 -
Rosie Perera said:
If that is indeed the workaround, then it's problematic that the PB compiler isn't case insensitive on the word "id".
Yes, it's case sensitive[:)]
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
Just make id = Id
Hi Dave,
I copied and pasted the line from the release notes into my PB document. The release notes has it as "id". Per your suggestion I tried "Id" and "ID" and even "INPUT ID" and "Input Id"- all get the same warning. The release notes indicate the attribute value is case sensitive, but it seems based on this experiment the attribute name isn't (at least this attribute name isn't).
The release notes has a space after "{{" and before "}}". I removed those spaces to look like your text and I still get the warning.
I even copied your text and pasted it into my document and I get the same warning.
The warning, though, is indicating a problem with the "type" attribute, not the "input id" attribute, so I tried your capitalization idea on the "type" attribute value ("Text" and "TEXT") and I still get the same warning.
0 -
Tim Hensler said:
The warning, though, is indicating a problem with the "type" attribute, not the "input id" attribute,
I initially received an error about input id, but after making the change the Warning:
[Warning] Unexpected attribute on element <input>: type
did not prevent the Input syntax from compiling and working with text.
However, I just tried {{input id=QUESTION_1 | type=text | width=4 | prompt=“Type”}} and it also worked, with the same warning as above. Hopefully Logos can enlighten us about the possible combinations[:D]
Dave
===Windows 11 & Android 13
0 -
Thank you for your help, Dave. I've fat-fingered more than one new feature so I needed someone to sanity check my work. I appreciate your help to confirm there does seem to be a problem.
0 -
I am able to reproduce this issue and will report it to Development.
0 -
This will be fixed in 5.1 release candidate 1.
0
