noscript problems? Just fixed ;-)
While I was writing precedent post I thought about a really simple solution, showed in this post using PHP but compatible with every server-side program language.
Head page doesn't accept a noscript tag but it accpets without problems one or more script tags.
If I'm not wrong, page download and parse is syncronous and that's mean that if I write a piece of code inside a script, next one will have this code ready or just executed.
Since downloading is syncronous, I can use this behaviour to save in a session this information and to show different layout using next tag.
The order is absolutely important to use this solution, just because first file need to do something like that:
while second file, page CSS, just need to show correct CSS, based on session JavaScript variable that will be setted only on JS enabled browsers:
At this point We should put a gz_handler inside CSS file
optimizing download speed for gz compatible browsers.
At the end, with a bit of immagination, We could directly use first script tag to append dinamically one or more dedicated stylesheet, returning just an empty string on page link request if JavaScript session var is set to true.
I hope this is a solution to solve W3 rules for a problem that "didn't exists" when (X)HTML was drafted for the first time ;-)
demo page
self brainstorming
Head page doesn't accept a noscript tag but it accpets without problems one or more script tags.
If I'm not wrong, page download and parse is syncronous and that's mean that if I write a piece of code inside a script, next one will have this code ready or just executed.
Since downloading is syncronous, I can use this behaviour to save in a session this information and to show different layout using next tag.
<head>
<script type="text/javascript" src="cssFilter.php"><!--// CSS Filter //--></script>
<link rel="stylesheet" media="all" href="myPage.php" />
</head>
The order is absolutely important to use this solution, just because first file need to do something like that:
<?php
session_start();
$_SESSION['JavaScript'] = true;
header('Content-Type: text/javascript');
exit('this;');
?>
while second file, page CSS, just need to show correct CSS, based on session JavaScript variable that will be setted only on JS enabled browsers:
<?php
session_start();
$output = file_get_contents(
isset($_SESSION['JavaScript']) && $_SESSION['JavaScript'] === true ?
'scriptEnabled.css':
'scriptDisabled.css'
);
header('Content-Type: text/css');
header('Content-Length: '.strlen($output));
$_SESSION['JavaScript'] = false;
exit($output);
?>
At this point We should put a gz_handler inside CSS file
ob_start('ob_gzhandler');optimizing download speed for gz compatible browsers.
At the end, with a bit of immagination, We could directly use first script tag to append dinamically one or more dedicated stylesheet, returning just an empty string on page link request if JavaScript session var is set to true.
I hope this is a solution to solve W3 rules for a problem that "didn't exists" when (X)HTML was drafted for the first time ;-)
demo page
Comments
Post a Comment