Closed
Bug 276253
Opened 20 years ago
Closed 20 years ago
View Source injects whitespace that does not exist
Categories
(Toolkit :: View Source, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 154120
People
(Reporter: cowwoc2020, Assigned: bugs)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Save the following code to an HTML file. Open it with FireFox then do "View
Source". You will notice that View Source is injecting spaces that do not exist
(looks like an off-by-one bug). Specifically, take a look at the first <span>
tag. In the original code, it reads: <span wcn = "[border]"> while under FireFox
it reads: <span wcn =" [border]">. Notice the space is shifted from before the
quote to inside it. The actual code follows:
------------------------
<html>
<body>
<span wcn = "[border]">
<table width = "0%" border = "0" cellspacing = "0" cellpadding = "1"
bgcolor = "black">
<tr>
<td width = "100%" valign = "top">
<table width = "100%" border = "0" cellspacing = "0"
cellpadding = "4" bgcolor = "white">
<tr>
<td width = "100%">
<span wcn = "[body]"/>
</td>
</tr>
</table>
</td>
</tr>
</table>
</span>
</body>
</html>
------------------------
Reproducible: Always
Comment 1•20 years ago
|
||
Already fixed on the trunk, ready for the next release. *** This bug has been marked as a duplicate of 154120 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
| Reporter | ||
Comment 2•20 years ago
|
||
Just to clarify: does FireFox routinely merge changes from the main branch or do I need to explicitly request that they port this change over to their codebase?
Comment 3•20 years ago
|
||
No, there is no need to ask for it to be ported. All changes on trunk will appear in the next release (Firefox 1.1).
Status: RESOLVED → VERIFIED
Comment 4•20 years ago
|
||
Still not fixed in V1.0.3.
Updated•16 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•