Closed normon66 closed 2 years ago
You can also see the additional p tag when you look at the field label in the Report. Labels for fields that come with a blank interview Example: First for first name in Q2 of default interview, don't have those additional p tags
It will no longer add the P tag automatically for new edits.
Existing P tags won't be removed. If it's already there, authors can clear the field and re-enter just the text.
Authors can press SHIFT+ENTER to continue using P tags like it was doing before if they wish.
This is still happening (or is happening again). After editing the labels of the two highlighted checkboxes in the image below, extra spacing appears. In the editor, a p is shown (second image) that explains this, which is also seen within the
Using A2J v A2J 9.0.0-2022-03-24
White testing the new Merge Components functionality in staging version A2J 10.0.0-0-2022-06-22, I noticed that this appears to be fixed.
When a field is first created (or had been imported from A2J4), the label sits right above the field, and the optional (Required) label is on the same line. However, if you edit the label, an extra
is inserted into the html via the edit box, causing a significant change in the vertical spacing via larger margins/padding, as well as bumping the (Required) label to the next line. Aesthetically and from an ease-of-use perspective, the (Required) works better on the same line as the label itself. Additionally, for a page with more than just a couple of fields, this uses up way more screen space than is needed, which could be an issue for mobile or tablet users, some laptop users, or those who have larger text sizes for accessibility purposes. It is possible (I do it all the time) to download the interview zip file, extract the guide.xml, perform a search and replace (which only works some of the time - other times you have to track them down one-by-one), replace the guide.xml in the zip file with the modified version, and reupload the entire zip to a2jauthor as a new interview. This can be rather time intensive, error-prone, bloats the content stored on the authoring server, and is likely beyond (and unknown) to a number of interview authors.
Verified in Chrome and Firefox, and has been an issue for at least a year.