Closed
Bug 72565
Opened 24 years ago
Closed 22 years ago
lines from source are displayed on page
Categories
(Core :: DOM: HTML Parser, defect)
Tracking
()
VERIFIED
INVALID
Future
People
(Reporter: mimi_fruchter, Assigned: harishd)
References
()
Details
(Keywords: testcase)
Attachments
(1 file)
(deleted),
text/html
|
Details |
At the top of the browsed page a source line is displayed:
<%@Language=VBScript%> <%session.codepage=1252%>
When viewing the source code page those lines appear at beginning
of the file bfore the <html> tag.
THESE LINES ARE NOT DISPLAYED WHEN USING Internet Explorer
Reporter | ||
Updated•24 years ago
|
Comment 1•24 years ago
|
||
I see the samething in 4.x Mac. This is not an i18n bug. Should we reassign this
to harishd ?
Comment 3•24 years ago
|
||
I see this on Linux too, build 2001-03-14-05 in strict and quirks mode and also
in 4.x
OS: Windows 98 → All
Updated•24 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
this is a fun bug, but mostly for other edge cases. I hope that ie is just being
stupid wrt its handling of the case exposed here.
Keywords: testcase
This bug has been marked "future" because the original netscape engineer working
on this is over-burdened. If you feel this is an error, that you or another
known resource will be working on this bug,or if it blocks your work in some way
-- please attach your concern to the bug for reconsideration.
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Comment 7•23 years ago
|
||
*** Bug 121018 has been marked as a duplicate of this bug. ***
Comment 8•23 years ago
|
||
This seems to be no bug... Apparently IE doesn't show the short asp-tags to
protect the asp-programmers. But we can expose them =P
The URL on this bug seems to be offline, but most certainly the short asp-tags
were disabled on that server.
I cannot reach w3.org either, what does the HTML/XML spec say what to do with
those tags ?
Comment 9•23 years ago
|
||
The URL http://hewbrew.tase.co.il/www/intro.asp does not seem to work anymore.
Changing to that of the duplicate.
Comment 10•22 years ago
|
||
We're doing the right thing; such tags should not be recognized as markup,
because the various symbols aren't valid name characters. And this is due to
server horkage, anyway. Resolving INVALID.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
Comment 11•20 years ago
|
||
*** Bug 276268 has been marked as a duplicate of this bug. ***
Updated•20 years ago
|
Status: RESOLVED → VERIFIED
Comment 12•19 years ago
|
||
(In reply to comment #10)
> We're doing the right thing; such tags should not be recognized as markup,
> because the various symbols aren't valid name characters. And this is due to
> server horkage, anyway. Resolving INVALID.
I'm curious what 'server horkage' is.
I am in control of both the server and the html code, but I am not sure how to
avoid mozilla/ff displaying this line of code (which was generated by DreamWeaver).
What are we supposed to do? What is the line supposed to do? Can I just remove it?
Comment 13•19 years ago
|
||
(In reply to comment #12)
> I am in control of both the server and the html code, but I am not sure how to
> avoid mozilla/ff displaying this line of code (which was generated by
DreamWeaver).
If your server sends those files WITHOUT processing them as 'asp' files, it's
your *misconfigured* server to blame.
> What are we supposed to do? What is the line supposed to do? Can I just remove it?
It depends. After removing them, it's just a valid HTML file, you have to remove
it. Otherwise, you have to fix your server configuration to process them 'as
asp' before emitting them out to the world. Your server should emit to the world
at large only VALID html files when it claims that they're 'text/html'.
Comment 14•19 years ago
|
||
(In reply to comment #13)
> (In reply to comment #12)
>
> > I am in control of both the server and the html code, but I am not sure how to
> > avoid mozilla/ff displaying this line of code (which was generated by
> DreamWeaver).
>
> If your server sends those files WITHOUT processing them as 'asp' files, it's
> your *misconfigured* server to blame.
>
> > What are we supposed to do? What is the line supposed to do? Can I just
remove it?
>
> It depends. After removing them, it's just a valid HTML file, you have to remove
> it. Otherwise, you have to fix your server configuration to process them 'as
> asp' before emitting them out to the world. Your server should emit to the world
> at large only VALID html files when it claims that they're 'text/html'.
>
>
An interesting dilemma: jungshik seems to be saying if the server doesn't
understand a particular sequence of characters as some kind of command, then
emit those characters. If the browser doesn't understand a particular sequence
of characters, then emit those characters. Yet, the user doesn't want to see
those characters... Clearly, "<% ... %>" is a server instruction, so maybe those
should all be stripped from the emitted HTML. However, "<% ... %>" is also a
valid HTML tag (just as "<p>" is, or "<whatever_i_want>" is), and should be
IGNORED by the browser (which firefox isn't doing). I think it's a firefox bug.
Comment 15•19 years ago
|
||
> However, "<% ... %>" is also a valid HTML tag
No, it's not. '%' is not an allowed character in HTML tag names.
You need to log in
before you can comment on or make changes to this bug.
Description
•