Closed Bug 453597 Opened 17 years ago Closed 17 years ago

External Style sheet doesn't doesn't execute in head

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Platform:
x86
Windows Vista
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: mp3geek, Unassigned)

References

(
URL
)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b1pre) Gecko/20080903145657 Minefield/3.1b1pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b1pre) Gecko/20080903145657 Minefield/3.1b1pre There is actually 2 issues here, Style sheet doesnt like to be moved into the HEAD, and the other bug, for some reason the button will move in 3.1a and not in 3.0 or Opera. Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: Stylesheet doesnt work when the style sheet is moved Expected Results: Move <LINK...> into <HEAD> </HEAD> should work. <LINK REL=stylesheet HREF="style.css" TYPE="text/css" media="screen"> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1"> </HEAD>
Style Sheet at the top: http://www.fanboy.co.nz/broken/moveme.html Style Sheet in the <Head> http://www.fanboy.co.nz/broken/moveme2.html
When <LINK> is at the top it blocks <!DOCTYPE> from being recognized so "moveme.html" is using "Quirks mode" and "moveme2.html" is using "Standards compliance mode". In Standards compliance mode we don't support accessing an element by its ID. Error Console reports: Error: business_dsl_span is not defined Source File: http://www.fanboy.co.nz/broken/moveme2.html Line: 22 In "Quirks mode" we do support it, with a warning in Error Console: Warning: Element referenced by ID/NAME in the global scope. Use W3C standard document.getElementById() instead. Source File: http://www.fanboy.co.nz/broken/moveme.html Line: 21 -> INVALID
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.