CDR Tickets

Interesting, indeed. Did they raise this issue when we were in negotiations with CBIIT about whether users would be forced to work on the bastion host? Also, it seems as if the two proposed solutions would have opposite effects. In other words, wouldn't increasing the resolution descrease the font size?

Example of how the "thickness" of the font looks different between the bastion host and their own computers.

In the linked issue WEBTEAM-625, Rob asks if this is something which can be controlled by the CSS rules we distribute to the client machines. Please investigate to determine whether we're already specifying font sizes for all of the text elements, and if not, whether we could address the users' concerns by adding some rules.

Robin, do you know if this is a problem only for the text in the SummaryMetaData block or for other elements as well?
I think I've been able to specify the font-width for those elements but we won't know for sure if the change has the expected effect until the modified CSS has been copied to PROD.

I've increased the font size in the CSS from 12pt to 14pt. This, however, may appear for some settings/monitors that the regular text looks like it's bolded.

Please have a look on DEV if this works better for everyone.

The general consensus at CIAT is that it looks better than before. It is definitely an improvement as it is much easier on the eyes.

We've received mixed feedback on this in ICRDB. We've noticed a few odd things, such as key points that now appear to be a smaller text size than surrounding text and bold text that now appears to be a larger font size than surrounding text. It's also harder to differentiate between bold text (in strong tags) and surrounding text, since everything appears to be bold.

However, since the majority (including CIAT) of folks are in favor of the change, we would like to apply it on production and see how it works for everyone. We will revisit this in a month or two to see if it is an acceptable change or if we should switch it back to 12pt (assuming that would not be hard to do). Thanks.

I'll check with CBIIT if this is something that can be updated outside of a release. If not we should add this ticket to the release since the work has already been done.

William/Robin, could you please notify the users that this change will likely appear today.

The following file has been copied on PROD:

• R12019: Summary.css

Please verify on PROD and close this issue.

Rob has updated the CSS file on PROD.

This item already made it to PROD which makes me believe that we can mark is as 'QA verified'.

Do we need to keep this ticket open?

Since neither William nor Robin are on this ticket I went ahead and closed it since the changes are already in production.

It looks like the changes to the fonts reverted the default or original one as reported in this issue. This happened after release 3.1. Could you please restore the changes?

Thanks for letting me know, William. I'm already working with Jim McMahon on another problem related to the synchronization of the XMetaL documents trying to find out what had been updated and when.
Please add a comment to the issue
https://tracker.nci.nih.gov/browse/WEBTEAM-1759
if you have permission or create a new one for OCECDR. I don't think we should add a change request to a completed issue unless you mark it as re-open.