Closed Bug 412114 Opened 17 years ago Closed 17 years ago

external javascript files cause page to fail to render

Categories

(Core :: General, defect)

Product:
Core
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: fta+bugzilla, Unassigned)

References

(
URL
)

Details

(Keywords: regression) 

This URL doesn't render anything in trunk while it does with Firefox 2.

(This bug comes from https://bugs.edge.launchpad.net/ubuntu/+source/firefox-3.0/+bug/182227)
Product: Firefox → Core
QA Contact: general → general
Keywords: regression
Flags: blocking1.9?
Keywords: regression
OS: Linux → All
Hardware: PC → All
WONTFIX per bug 305873. See also bug 393281 and bug 408702. That script tag needs to be closed, and ending it with "/>" isn't the proper way to do that in HTML.
Blocks: 305873
Status: NEW → RESOLVED
Closed: 17 years ago
Flags: blocking1.9?
Resolution: --- → WONTFIX
Thanks. I've closed the Ubuntu bug too.
Please re-open this.

According to the W3C validator, <script /> is valid XHTML-transitional 1.0, and the same problem occurs there.

The following HTML validates with W3C and fails to render in FF3:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
		"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
	<title>LedgerSMB 1.2.99</title>
	<meta http-equiv="Pragma" content="no-cache" />
	<meta http-equiv="Expires" content="-1" />
		<link rel="shortcut icon" href="favicon.ico" type="image/x-icon" />
	
	<link rel="stylesheet" href="css/ledgersmb.css" type="text/css" title="LedgerSMB stylesheet" />
	
	
	<link rel="stylesheet" href="UI/login.css" type="text/css" title="LedgerSMB stylesheet" />
	
	<link rel="stylesheet" href="css/ledgersmb.css" type="text/css" title="LedgerSMB stylesheet" />
	
	
	<script type="text/javascript" language="JavaScript" src="UI/login.js" />
	
	


	<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
	<meta name="robots" content="noindex,nofollow" />
        
</head>


		 


<body class="login" onload="setup_page('Name:',
	'Password:');">
	<br /><br />
	<center>
		<form method="post" action="login.pl" name="login"
			onsubmit="return submit_form()">
		<input id="menubar" type="hidden" name="menubar" value="" /> 
		<input id="blacklisted" type="hidden" name="blacklisted" value="" /> 
		<div class="login">
			<div class="login" align="center">
				<a href="http://www.ledgersmb.org/" target="_top"><img src="images/ledgersmb.png" class="logo" alt="LedgerSMB Logo" /></a>
				<h1 class="login" align="center">Version SVN Trunk</h1>
				<div align="center">
					<div id="credentials"></div>
					<div id="company_div">
					  <div class="labelledinput">
						<div class="label">
							<label for="company">
							Company
							</label>
						</div>
						<div class="input">
							<input class="login" 
							type="text" 
							name="company" 
							size="30"
							id="company" 
							accesskey="c" />
						</div>
					</div>
				</div>
				<button type="submit" name="action" value="login" accesskey="l">Login</button>
			</div>
		</div></div>
		</form>
		<p><a href="admin.pl">Administrative login</a></p>
	</center>
</body>
</html>
Or should I open a new bug since this is specific to XHTML?
Chris, you're misinterpreting the validator output.  See http://slashdot.org/comments.pl?sid=556436&cid=23453592 for an explanation.
Thanks for the explanation.  I apologize for being overly frustrated with this issue.  I spent four or five hours looking through commit logs on the application I was debugging only to discover it was an unintentional upgrade of FF which caused the problem (when I upgraded my Linux distro).  I can't imagine I am alone in this :-)

FWIW, this highlights the fact that this is a fairly disruptive change, and one I would expect to substantially slow down adoption of FF3 as well as cause scores of duplicate bugs.  Since this probably isn't going to change, I would *highly* suggest putting together a form letter which suggests fixes to the page.  In fact, if you would like, I would be happy to submit a draft to you.
As a side not, using link tags for external Javascript is not well supported across browsers, which would probably be an otherwise ideal solution....

How about something like:

Thank you for reporting this issue with us.  Due to past issues with the script tag (see  bug 305873), we have changed Firefox behavior relating to this tag to require a more strict following of the spec (insert link here).  We expect that this will prevent other problems in the future.  See http://developer.mozilla.org/en/docs/Updating_web_applications_for_Firefox_3#Change_to_the_SCRIPT_element for a summary.

We don't plan to change how we handle the script tag to accomodate empty script tags.

You have two options for fixing your application depending on the type of document.  HTML applications require a closing tag (<script src="..."></script> instead of <script src="..." />).  XHTML applications can use the above method or send out a MIME type of application/xhtml+xml to the application.

If you are not the maintainer of this web page, we cannot help you, but you can forward this message to the webmaster of the affected site.
You need to log in before you can comment on or make changes to this bug.