#11874 [Opn->Bgs]: <script> way of inline'ing PHP has quite strict syntax

From: Date: Fri, 02 Sep 2005 12:05:52 +0000
Subject: #11874 [Opn->Bgs]: <script> way of inline'ing PHP has quite strict syntax
References: 1  Groups: php.doc 
Request: Send a blank email to phpdoc+get-969369828@lists.php.net to get a copy of this message
ID: 11874 Updated by: vrana@php.net Reported By: vinicius at empresa-digital dot com dot br -Status: Open +Status: Bogus Bug Type: Documentation problem Operating System: Any PHP Version: Irrelevant New Comment: Documentantion is clear enough about it. Previous Comments: ------------------------------------------------------------------------ [2001-07-04 19:25:51] jeroen@php.net The script way of inline-ing php only works with <script language="php">, and nothing else (no other attributes). This is a speed issue: Zend doesn't implement a whole html-parser just to support this... in only accepts whiteshace difference and case-diffs. There is no use for this too, since it will *not* be send to the browser. (RTFM on 'What it PHP': a preprocessor) Documentation should be more clear on this, so changed to an open documention bug. For the documenter: may add example that the context is not important? (i.e. <font size="<script php>echo '+1'</script>"> works) ------------------------------------------------------------------------ [2001-07-04 13:26:27] derick@php.net I don't get what you are meaning here. Can you add an example of a whole line of both cases (one with the error, and one that works)? Derick ------------------------------------------------------------------------ [2001-07-04 07:31:00] vinicius at empresa-digital dot com dot br The attribute 'content' inside '<script' tag is not being properly recognized in version 4.0.5. If I insert it, the preprocessor returns an error condition. If I strip it, everything works fine. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=11874&edit=1

« previous php.doc (#969369828) next »