566032 - Symantec internal Web page displays incorrectly due to missing trailing ")" in CSS

Status: RESOLVED FIXED

(Tech Evangelism Graveyard :: English US, defect)

Description

[Bob McGowan]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3

Internal web page for the group I work with looks fine in FF 3.5.9, with side panel (white background) with links and a central area that displays results of clicking a link in the side panel.

In FF 3.6.3, the links are on the left with a grey background, and everything that should be showing up in the center shows up underneath/below.

One of the groups web developers thinks it is a DIV tag issue.

I have screen shots to attach of the two situations.  As there is no apparent way to do that from this page, I will have to deal with it later.

Reproducible: Always

Steps to Reproduce:
Since this is an issue with an internal web page and I have not seen the problem elsewhere, I can only suggest (at this point) supplying a copy of the code in use for analysis.
Actual Results:  
See attached image file:

  actual:  FF363_toolspage.jpg

Expected Results:  
See attached image file:

  expected:  FF359_toolspage.jpg

I have run FF 3.6.3 in -safe-mode to disable all extras and it still displays incorrectly.

Comment 1

[Mardeg]

please attach the code of the page and related css files to this bug.

Comment 2

[Bob McGowan]

Attachment: FF 3.5.9 image of correctly displayed web page

Comment 3

[Bob McGowan]

Attachment: FF 3.6.3 of incorrectly display web page

Comment 4

[Bob McGowan]

Should I tar/zip/ar the two files, since they are HTML/etc??

Comment 5

[Bob McGowan]

Attachment: main web page code, obtained using View->Page Source and Save As

I have cleaned out system and user names.  There should be nothing left that could be considered proprietary, a breach of confidence or privacy.

I also removed the path part of the stylesheet href so this and it can be in the same directory.

Image files are not included but don't affect the display.

Comment 6

[Bob McGowan]

Attachment: style sheet file for the tools.htm attachment.

Comment 7

[Bob McGowan]

(In reply to comment #4)
> Should I tar/zip/ar the two files, since they are HTML/etc??

Sorry, didn't think about this - not an issue to worry about.

Comment 8

[j.j.]

Same result on Win XP with 1.9.3 trunk and Opera 10.53
Works as reporter expects with WebKit and IE8.
Will try to reduce.

Comment 9

[j.j.]

Please validate your CSS. A missing ")" after |Div.gif| is causing this.


A.mastheadLink, A.mastheadLink:visited {color:#000; padding:3px 10px 3px 10px; background:url(../images/nav_new/mastheadDiv.gif no-repeat right}
		A.mastheadLink:active, A.mastheadLink:hover {color:#FFF; padding:3px 10px 3px 10px; background:#F27F1A url("images/nav_new/mastheadDiv.gif") no-repeat right}

#contentWrapper {position:relative; float:left; width:800px; background:#FFF}

Comment 10

[j.j.]

Attachment: testcase

Looks like a WebKit bug (not wondering about IE8)

Comment 11

[philippe (part-time)]

That is the same issue as bug 537078, or bug 523317, which are all due to bug 476856 (stricter parsing of url()). Moving to TE.

Fixing the error in the stylesheet is the solution.

Comment 12

[Chris Lawson (gone)]

Assigning to Bob, since presumably he's in a position to pass the solution on to the right people and is the only one who can tell us if they fix it.

Comment 13

[Bob McGowan]

The developer resonsible for the style sheet template has confirmed the problem and fixed it.

Thank you for the help with this.  FYI, I've created a simple Perl script that reads a file and counts opening/closing pairs, reporting the counts.  This will be used in the future to be sure things are properly balanced.

So I shouldn't be bothering anyone with this type of problem, in the future. ;)

As far as I'm concerned, this incident can be closed.  Question is, should I?

Comment 14

[Chris Lawson (gone)]

Since you're the only one who knows whether it's been fixed, yeah, you'd be an appropriate person to close it :)

cl

Comment 15

[Bob McGowan]

OK ;)

My primary concern was with getting any "protocol" elements done correctly.

So, I'm changing status to RESOLVED and FIXED, as this fits best, from my perspective.

It may not, from your end, as the "fix" is outside of your control.

Comment 16

[Chris Lawson (gone)]

That'll work, and it's exactly how we like to see TE bugs resolved. Thanks for your help here, Bob.