ansaurus

Question

ok to include css and js files outside <html>?

Answer 1

+5 A:

Will not be valid (X)HTML.

Alan Haggai Alavi 2010-02-01 01:14:13

but how come that it works on firefox?

weng 2010-02-01 01:16:07

Working, and validating are different. Google's pages work in all browsers, however, they do not validate successfully.

Alan Haggai Alavi 2010-02-01 01:17:02

Browsers are made to do the best they can to cope with broken HTML, so Firefox is doing what it can. It probably puts in an implicit <html> at the start and discards the next one.

Alex JL 2010-02-01 01:41:14

I've seen title tags at the bottom of a page. Browsers are extremely forgiving. Maybe too forgiving.

John Conde 2010-02-01 02:44:49

Answer 2

+6 A:

This isn't valid html. The best place to put the javascript would be before the body close (unless there's in-line scripts that need those scripts to be loaded). This prevents blocking as the page loads.

Nick Craver 2010-02-01 01:14:58

It's not valid HTML anyway, there's no DTD.

bdl 2010-02-01 01:49:59

Answer 3

+2 A:

This will work in most all browsers, but that's not to say it isn't wrong. It is wrong.

It's not valid HTML, and will confuse just about everyone who comes across your code, and though I don't know what browsers could possibly fail to overcome the inherent wrongness about this style, I make no promises that it will work. In a sense, it should, but in another, it most definitely should not.

Matchu 2010-02-01 01:17:13

Answer 4

+9 A:

Even if it works, you shouldn't do it. This type of stuff is sloppy, and as such isn't guaranteed to work tomorrow, or in future browsers. If you don't feel the agony of this method now, you will eventually. There's no reason that you should be doing this anyway.

Jonathan Sampson 2010-02-01 01:17:41

true.but then again, many frameworks use this technique and keep them in a separate php file.

pixeltocode 2010-02-01 11:37:04

@pixeltocode: You can do that and still load them up in the proper place.

Jonathan Sampson 2010-02-01 12:51:43

Answer 5

+1 A:

Perhaps output buffering will work in this situation? Buffer the output from your "includes" file, then grab the contents of the buffer to output later, after the <html> declaration. Something roughly like this:

In your includes.php file:

<?php 
ob_start();
// here is where you output your css and js declarations
$includes = ob_get_clean();
?>

And here is your main page:

<html>
 <head>
  <title>Hello</title>
  <?php echo $includes ?>
 </head>
 <body>
 ...

pbarney 2010-02-04 07:05:42

ansaurus

tags:

views:

answers:

ok to include css and js files outside <html>?

related questions