tags removed from source code

The main difference is that all my "</option>" tags are missing in the
"Source code". Because of that, the "<optgroup>" tag isn't recognized
at all in IE ( "</option>" tags are also missing in IE when I view the

<select>
        <optgroup label="My group">
                <option value="1">A
                <option value="2">B
                <option value="3">C
                <option value="4">D
        </optgroup>
</select>

<select>
        <optgroup label="My group">
                <option value="1">A</option>
                <option value="2">B</option>
                <option value="3">C</option>
                <option value="4">D</option>
        </optgroup>
</select>

> Hi,
>
> for some reasons, with the "Web Developper bar" in Firefox, I
> discovered that there are differences between the "Source code" and
> the "Generated source code" in my application.
>
> The main difference is that all my "</option>" tags are missing in the
> "Source code". Because of that, the "<optgroup>" tag isn't recognized
> at all in IE ( "</option>" tags are also missing in IE when I view the
> source code ).
>
> Source code:
>                 <option value="1">A
>                 <option value="2">B
>                 <option value="3">C
>                 <option value="4">D
>
> Generated source code:
>
> So can someone tell me why both FF and IE remove these closing tab?

> Another strange thing I noticed: I copied the "Generated source code"
> and put it in a new file, and if I open the file in FF or IE,
> everything is working well. So I don't understand when this kind of
> filtering is applied. Anyone know?

> twiggy182 wrote:
> > Hi,
> > for some reasons, with the "Web Developper bar" in Firefox, I
> > discovered that there are differences between the "Source code" and
> > the "Generated source code" in my application.
> > The main difference is that all my "</option>" tags are missing in the
> > "Source code". Because of that, the "<optgroup>" tag isn't recognized
> > at all in IE ( "</option>" tags are also missing in IE when I view the
> > source code ).
> > Source code:
> > =A0 =A0 =A0 =A0 =A0 =A0<option value=3D"1">A
> > =A0 =A0 =A0 =A0 =A0 =A0<option value=3D"2">B
> > =A0 =A0 =A0 =A0 =A0 =A0<option value=3D"3">C
> > =A0 =A0 =A0 =A0 =A0 =A0<option value=3D"4">D
> > Generated source code:
> > So can someone tell me why both FF and IE remove these closing tab?
> I don't understand. You are showing that the browser is *adding* the
> closing tags. The "source code" is the code received by the browser. The
> "generated source code" is what the browser spits out when it recreates
> a well-formed HTML document from its in-memory DOM tree (that is, its
> internal representation of the document).
> > Another strange thing I noticed: I copied the "Generated source code"
> > and put it in a new file, and if I open the file in FF or IE,
> > everything is working well. So I don't understand when this kind of
> > filtering is applied. Anyone know?
> What do you mean by "filtering"? Naturally the page looks the same.
> You're feeding the browser exactly the same code that it considered to
> be equivalent to the DOM tree it built the first time around.

> wrote:
>> twiggy182 wrote:
>>> Hi,
>>> for some reasons, with the "Web Developper bar" in Firefox, I
>>> discovered that there are differences between the "Source code" and
>>> the "Generated source code" in my application.
>>> The main difference is that all my "</option>" tags are missing in the
>>> "Source code". Because of that, the "<optgroup>" tag isn't recognized
>>> at all in IE ( "</option>" tags are also missing in IE when I view the
>>> source code ).
>>> Source code:
>>> <option value="1">A
>>> <option value="2">B
>>> <option value="3">C
>>> <option value="4">D
>>> Generated source code:
>>> So can someone tell me why both FF and IE remove these closing tab?
>> I don't understand. You are showing that the browser is *adding* the
>> closing tags. The "source code" is the code received by the browser. The
>> "generated source code" is what the browser spits out when it recreates
>> a well-formed HTML document from its in-memory DOM tree (that is, its
>> internal representation of the document).
>>> Another strange thing I noticed: I copied the "Generated source code"
>>> and put it in a new file, and if I open the file in FF or IE,
>>> everything is working well. So I don't understand when this kind of
>>> filtering is applied. Anyone know?
>> What do you mean by "filtering"? Naturally the page looks the same.
>> You're feeding the browser exactly the same code that it considered to
>> be equivalent to the DOM tree it built the first time around.
>
> Hi Harlan,
>
> by "Source Code" and "Generated Source Code" I refer to the terms used
> by "Web Developper" bar in FF. Just to clarify a little bit:
> Source code: The code used to display the page
> Generated source code: The code generated by the application, which is
> what the browser receives as input

"http://www.w3.org/TR/html4/strict.dtd">

                <p>Try this.

<html><head>

                </head><body><p>Try this.

</p></body></html>

code, will display the tags for them, as well as the closing </p> tag.

> So the browser is in fact *removing* the closing tags in a given
> filtering process.

> Example: create a web page containing:
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
> <p>Try this.
> Load it in Firefox. "View source" will give you the above.

> "View
> generated source" will give you:
> </head><body><p>Try this.
> where Firefox will have created the required html, head, and body
> elements in its internal model,