275201 - usc.edu - A display error prevented me from filling out a college application online with Firefox.

Status: RESOLVED INCOMPLETE

(Tech Evangelism Graveyard :: English US, defect)

Description

[otaconjon]

I was filling out the University of Southern California's online application for
admission and when I got to the 'coursework' page (note: this is inside a secure
link that requires log-in), that which should have appeared as a drop-down menu
appeared as a jumbled block of the text that would have been in said drop-down
menu. Because of this, I was blocked and unable to proceed with the online
application using Firefox. I contacted USC technical support and they said that
they would look into it, but that I should also file a bug report with you. I
ended up using Internet Explorer to complete the application; the menu worked
for that browser, so it must be a problem in compatibility between Firefox and
the USC website.

Comment 1

[Bill Mason]

Unless you can give us a testcase or at least a copy of the source code from the
page in question, there's nothing we're going to be able to do with this report
-- since no one is going to have a login for this system.

Comment 2

[otaconjon]

Attachment: Screenshot of the error on Firefox.

Here is what it looks like in Firefox.

Comment 3

[Bill Mason]

(In reply to comment #2)
> Created an attachment (id=169058) [edit]
> Screenshot of the error on Firefox.
> 
> Here is what it looks like in Firefox.

A screenshot tells us nothing useful.  If we can't get some sample of the source
code, then this bug is invalid.

Comment 4

[otaconjon]

Attachment: Source code.

Here is a copy of the source code of one of the pages (they all follow the same
format in the menu in question).

Comment 5

[otaconjon]

(In reply to comment #3)
> (In reply to comment #2)
> > Created an attachment (id=169058) [edit] [edit]
> > Screenshot of the error on Firefox.
> > 
> > Here is what it looks like in Firefox.
> 
> A screenshot tells us nothing useful.  If we can't get some sample of the source
> code, then this bug is invalid.
> 
No need to be snide. There is your source code. I don't know what else you want
me to give.

Comment 6

[Bill Mason]

(In reply to comment #5)
> (In reply to comment #3)
> > (In reply to comment #2)
> > > Created an attachment (id=169058) [edit] [edit] [edit]
> > > Screenshot of the error on Firefox.
> > > 
> > > Here is what it looks like in Firefox.
> > 
> > A screenshot tells us nothing useful.  If we can't get some sample of the source
> > code, then this bug is invalid.
> > 
> No need to be snide. There is your source code. I don't know what else you want
> me to give.
> 

I'm not being snide.  You gave us a screenshot, I explained to you that means
nothing to diagnosing a bug.  It's not my problem that you wrote a bug report
with no information to diagnose it with.

That said, the source code renders the same for me in Moz and IE6 when I add a
<base> tag to load the CSS and images.

I would suggest this move to a TE bug.  It's probably going to be up to the page
authors to fix the issue.

Comment 7

[otaconjon]

(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #3)
> > > (In reply to comment #2)
> > > > Created an attachment (id=169058) [edit] [edit] [edit] [edit]
> > > > Screenshot of the error on Firefox.
> > > > 
> > > > Here is what it looks like in Firefox.
> > > 
> > > A screenshot tells us nothing useful.  If we can't get some sample of the
source
> > > code, then this bug is invalid.
> > > 
> > No need to be snide. There is your source code. I don't know what else you want
> > me to give.
> > 
> 
> I'm not being snide.  You gave us a screenshot, I explained to you that means
> nothing to diagnosing a bug.  It's not my problem that you wrote a bug report
> with no information to diagnose it with.
> 
> That said, the source code renders the same for me in Moz and IE6 when I add a
> <base> tag to load the CSS and images.
> 
> I would suggest this move to a TE bug.  It's probably going to be up to the page
> authors to fix the issue.

Under the bug reporting guidelines, nowhere does it say that a screenshot is
unacceptable or that a complete copy of the source code is required. Therefore,
based on what I have seen in other bug reports, I found my report in this
instance to be a reasonable start to solving the issue at hand.
In any case, I will inform the USC technical support department of your
diagnosis. Thank you for your time.

Comment 8

[Mats Palmgren (inactive)]

<DEADBEEF:COMBOBOX size="17"  name="TempAcademicHist::TitleEngSem11" >
  <option selected VALUE="English I H"> English I H<option value='1'> ...
</DEADBEEF:COMBOBOX>

If I change DEADBEEF:COMBOBOX to SELECT then the page works fine.


-> TE

Comment 9

[Matthias Versen [:Matti]]

Is this stil an issue ?

Comment 10

[Chris Lawson (gone)]

INCOMPLETE due to lack of activity since the end of 2009.

If someone is willing to investigate the issues raised in this bug to determine whether they still exist, *and* work with the site in question to fix any existing issues, please feel free to re-open and assign to yourself.

Sorry for the bugspam; filter on "NO MORE PRE-2010 TE BUGS" to remove.