PHP Forum

**racer x** · 01-23-2009, 06:28 PM

I have been using chrome a bit more since Firefox had been freezing(!) on me so many times. I have come to really like it.
However...
I am practicing PHP on local host with xampp and when I view the source of a page I am working on it does not show echoed variables or any parsed text for that matter. eg value="" (that's all that is printed to source code)

Parsed text IS printed to the page in the browser as normal.

Note: The exact same page source viewed in Firefox works fine showing all parsed variables and info.

Is this some kind of security thing Chrome has introduced?

**Decaf** · 01-23-2009, 06:52 PM

1) Maybe it is a security thing
2) Is the text being printed before the <html> tag?
3) A source code snippet would help.
4) Are you connecting through the http://localhost or file:C/...

**racer x** · 01-23-2009, 08:58 PM

1. I've done some reading and wonder if chrome will only display parsed text in source code if it is done with htmlentities() ? I am just learning form validation in php(and client-side). One php book I have (Codin' for the Web) doesn't even mention htmlentities while another book(Learning php & msql O'reily) uses it everywhere.

2. The code source looks exactly as normal source code view does, the only difference being that the parsed variables are not shown in the source.

3. Here is a snippet of the same exact viewed source code from a form:
(in chrome) value=""
(in Firefox) value="Joe"
The actual php on the form is: value="<?php echo $name ?>"

4. I am connecting through http://localhost/form_testing/form.php

Again, the variables are all showing up on the page correctly. Everything works on my validation etc. This was just something I was wondering about how chrome handles source code.

Maybe if you have some php pages on localhost that you can open with chrome you'll see what happens.

OK. I've looked at a bunch of PHP sites and viewed their source code. They seem to be displaying everything. I will look my page over again.

**NullPointer** · 01-23-2009, 09:12 PM

PHP is server side code. It doesn't care which browser the user has and acts the same regardless. If there is a problem with how something is displaying in chrome vs firefox vs IE or whatever then the problem is with PHP's output, not the PHP code itself. Unless you deliberately identify and tell PHP to do something different based on a users browser, the output will be the same.

**racer x** · 01-23-2009, 10:56 PM

When I was originally testing for errors it would print "you must fill in your name(etc)" but when I viewed the source code that code/text was not there where it would normally be after parsing.

Maybe has something to do with the form being sticky and resubmitting to itself? When that new page is displayed with previous input, etc. none of it shows up in the code but it does in the browser.

You would think if it was printing the input from previous attempts automatically that that would have to show up in the source?

**Decaf** · 01-23-2009, 11:35 PM

Quote:

Originally Posted by racer x

When I was originally testing for errors it would print "you must fill in your name(etc)" but when I viewed the source code that code/text was not there where it would normally be after parsing.

Maybe has something to do with the form being sticky and resubmitting to itself? When that new page is displayed with previous input, etc. none of it shows up in the code but it does in the browser.

You would think if it was printing the input from previous attempts automatically that that would have to show up in the source?

1) The PHP Source will have that error somewhere. It can't print "mystery"/"unknown" text, however if it is an parse/syntax error it will display a warning but that's not your problem

2) We will only have to guess without an example of the code.