We are using the following java code:
radioHTMLText.append("<td style=“vertical-align: top;”>");
String rValue = aDoc.getItemValueString(“Answer”);
for (String choice : choices)
{
radioHTMLText.append("<span style=“vertical-align:top;”>");
if(choice.equalsIgnoreCase(rValue)){
radioHTMLText.append("<label style=“vertical-align: top;”><input style=“vertical-align: top;” checked type=“radio”>");
}else{
radioHTMLText.append("<label style=“vertical-align: top;”><input style=“vertical-align: top;” type=“radio”>");
}
radioHTMLText.append(StringUtils.trim(choice));
radioHTMLText.append(" ");
radioHTMLText.append("</span>");
radioHTMLText.append("</label>");
if(qRecord.getItemValueString("QuestionOrientation").equalsIgnoreCase("pageDirection")){
radioHTMLText.append("<br />");
}
}
radioHTMLText.append("</td>");
radioHTMLText.append("</tr></tbody></table>");
builder.insertHtml(radioHTMLText.toString(),true);
we have placed the “vertical-align:top;” on every tag, but it is not honored in the resulting output.
See document example.image.png (21.7 KB)
@paul.calhoun,
Please copy the problematic HTML string in a .txt/.html file, ZIP and attach the file here for testing. We will investigate the issue on our end and provide you more information.
here are the three source files that demonstrate the issue.Temp.zip (8.1 KB)
@paul.calhoun,
We are working over your query and will get back to you soon.
@paul.calhoun,
Thanks for your inquiry. We tested the scenario and have managed to reproduce the same problem on our end. For the sake of any correction, we have logged this problem in our issue tracking system. The ID of this issue is WORDSNET-16844. We will further look into the details of this problem and will keep you updated on the status of this issue. We apologize for your inconvenience.
I need an update on this please. We need to put our code in production and this is keeping us from deploying.
@paul.calhoun,
Thanks for your inquiry. Unfortunately, your issue (WORDSNET-16844) is not resolved yet. We are currently doing analysis of this issue to determine the root cause. Once the analysis of this issue is completed, we may then be able to share estimates with you. Rest assured, we will inform you via this thread as soon as this issue is resolved. We apologize for your inconvenience.
@paul.calhoun,
Regarding WORDSNET-16844, we have identified the root cause of this issue and are going to implement a fix. Please check this new output DOCX file (see new-output-fixed.zip (14.1 KB)). This output illustrates the fix that we are going to implement.
Please tell if this new output is acceptable for you?
Yes, that is acceptable and looks much better.
Thank you.
@paul.calhoun,
Thanks for your feedback. We will inform you via this thread as soon as this issue is resolved.
@paul.calhoun,
If this issue (WORDSNET-16844) is important to you, and for the fast resolution of this issue, please have a look at paid support options - e.g. purchasing Paid Support will allow you to post your issue(s) in our Paid Support Helpdesk and raise the priority of this issue for fast resolution. Many Paid Support customers find that this leads to their issue being fixed in the next release of the software.
If you would like to take advantage of Paid Support then please request a quote in our purchase forum - Aspose.Purchase - Free Support Forum - aspose.com