CDR Tickets

Low priority. We will likely not address this until after cutover.

Can I put this ticket in the "On Hold" status?

Added Robin as a watcher, as I think she might have been the original source of the report of the problem.

I did some more research on this, and it doesn't look like a problem that will be easy to solve. I think we'd need to use images for the square bullets. I was tempted to close this, since CBIIT has said they're going to remove the requirement they imposed that we do all our CDR work on the bastion host, but then I thought it might be good to dump all the remaining bastion host problems in their lap in the event that they renege on that commitment.

I am seeing that the second level bullets (squares, actually) appear to be a little bit larger in IE on the bastion host compared to other browsers or IE on my desktop but it is by far not as obvious as listed on the screen shot.

Robin, maybe you could double-check if this problem still exists for you before I report is to CBIIT?

I'm attaching a screenshot from prod this morning. The square bullets are still pretty large - they look to be the same as the original screenshot posted to this issue.

Which report are you running - RS or BU? I want to make sure I'm looking at the exact same report.

This was BU for CDR62865.

Attached is the screenshot I see for the summary Robin listed. Works for me. :-)

I'm trying to show the screenshot with a similar size to Robin's.

OK, it appears this behavior is user dependent. You should feel lucky to be special.

I'll submit a ticket to CBIIT.

The bullets I see look like the ones Robin sees, so she's not the only one (screen shot attached). So CBIIT needs to figure out what's different between our profiles and yours, Volker, and then they need to figure out how to eliminate the problem permanently.

Doing a little more investigation the problem is not the fact that we're dealing with sub-bullets and it's not a problem with the CSS. Instead, the default list-style-type "square" has been put on steroids by IE. I've created two samples on PROD, the first specifying the list-style-type with CSS, the second lets IE pick the appropriate list-style-type (no CSS).

(paste the URL into your browser)
file:///c:/tmp/bullets.html

file:///c:/tmp/bullets2.html

I've submitted a ticket to CBIIT (WEBTEAM-4817)

I got an answer from CBIIT indicating that the bullets will look "normal" in IE9 once the compatibility view has been turned on. I can confirm that the square do look better in compatibility view but I can't say if the summary overall will still look OK. Since I don't see this problem in the summaries could one of you, Bob or Robin, check out if changing to compatibility view would solve the display problem with bullets without messing up the page display over all?

Turn on compatibility view by going to the IE menu

 Page --> Compatibility View Settings

and set the checkbox for Display all websites in Compatibility View.

That seems like the wrong solution, from my vantage point. Perhaps we should consult with Mark and his colleagues to get a more informed perspective, but my understanding of compatibility mode is something along the lines of "the HTML code I'm trying to display is messed up, so please emulate the bugs present in the earlier versions of the browser that made things look OK in spite of the poor markup." First of all, I don't think our markup is incorrectly formed, but if it were the right solution to that problem would be to fix it. Second, the same markup looks just fine in standards mode on my own desktop, so it seems more likely that the breakage is in the configuration of the bastion host.

I completely agree with you. As I understand it the problem is a bug in IE9. I just wanted to get an idea of what might break if one switches to compatibility mode just to "fix" the bullets since I'm unable to test this.
The solution seems to be upgrading IE but we can't do that without breaking the current XMetaL/CDRClient.

I'm wondering if this is still an issue since we moved off the bastion host.

Changed status from On Hold so we can talk about this ticket at our CDR status meeting.

We're not on the bastion hosts any more, so this problem is gone.