Closed
Bug 57722
Opened 24 years ago
Closed 7 years ago
view-source leaves out whitespace at end of document
Categories
(Core :: DOM: HTML Parser, enhancement)
Core
DOM: HTML Parser
Tracking
()
People
(Reporter: jruderman, Unassigned)
References
(Depends on 2 open bugs)
Details
(Whiteboard: BLOCKED)
Attachments
(2 files)
If an html page contains only whitespace (spaces, tabs, and Windows newlines),
view source won't display anything. I should be able to select text to see how
much whitespace there is.
occurs at:
javascript:" "
javascript:" \n \n "
doesn't occur at:
javascript:" \n 3 \n " because it contains a non-whitespace character
And then there's the empty-line issue.. afaict the only way to tell if Mozilla
thinks there's a newline at the end of a short document is to scrunch the view-
source window. That's somewhat more counter-intuitive than selecting to
determine the presense of spaces :)
Maybe the style sheet should be changed so that text background is a different
color than what it is now. I think w3.org uses all sorts of interesting
styles, many of which would help.
OS: Windows 98 → All
Hardware: PC → All
Basically, clicking anywhere w/ the text will cause the entire text region to
be semi yellowed. I know that css can add borders to objects, but it migt be
useful if we could -moz- style lines of <pre> so that you could have a border
around the whitespace (instead of or in addition to the background coloring).
Hixie: thoughts?
Comment 4•24 years ago
|
||
Agreed that you should be able to select the whitespace, for pure correctness
reasons, but why on earth would you want to check anyway?
This can be fixed when we go back to XML view source and the view source window
is styled using CSS again. Feel free to assign to me if you would want me to
mess with the styles in the way suggested by timeless once we are there again.
Keywords: correctness
Reporter | ||
Comment 5•24 years ago
|
||
>why on earth would you want to check anyway?
I want to know why bug 57717 doesn't affect data: urls.
Based on Ian's comment I'm reassigning the bug to him.
Assignee: harishd → ian
Status: ASSIGNED → NEW
Comment 7•24 years ago
|
||
This won't be fixed by me unless we switch back to an XML-based view source.
We won't switch back to XML-based view source until genererated content is
selectable. I can't find either of those bugs, but this is dependent on those.
Severity: major → enhancement
Component: Parser → XP Apps: GUI Features
Keywords: donttest
Priority: P3 → P4
Whiteboard: BLOCKED
Target Milestone: mozilla0.9.1 → mozilla1.2
Comment 9•24 years ago
|
||
OK. We are still doing HTML view source.... but we are now using a stylesheet.
Hixie, could you take a look into this again?
Word of warning -- regular #text nodes in the source do not currently get their
own <span> elements, but those could be reinstated (at a very slight perf hit).
The generate content bug is bug 12460
Depends on: 12460
Comment 10•24 years ago
|
||
I can't do anything here without a UI spec, since I don't know what would be
best. Handing off to UID. Send it back when a spec is ready and I'll triage it
if it is beyond my meager skills. :-)
Assignee: ian → mpt
Component: XP Apps: GUI Features → User Interface Design
QA Contact: sairuh → zach
Reporter | ||
Comment 11•24 years ago
|
||
Also happens at javascript:"3\n<b> \n ". Everything after the <b> is cut off.
Summary: view-source shows nothing on whitespace-only pages → view-source leaves out whitespace at end of document
Comment 12•24 years ago
|
||
Erm ... What do you want here? Some sort of toggle which will hide/show
whitespace characters as little dots and pilcrows and stuff?
The more I see these sort of bugs, the more I think View Source should just be
handled by the helper app which the user has chosen for text/plain.
Reporter | ||
Comment 13•24 years ago
|
||
I don't care if Mozilla shows the whitespace, I just want to be able to select
it like I can select normal text or whitespace that isn't at the end of the
document. (Btw, if I do Ctrl+A and copy from view source, I do get the
whitespace, but I can't see the selected whitespace in the view-source window)
Comment 14•24 years ago
|
||
*** This bug has been marked as a duplicate of 57724 ***
Comment 15•23 years ago
|
||
Reopening 57724 dependencies for independent resolution.
Comment 16•22 years ago
|
||
.
Assignee: mpt → doron
Status: REOPENED → NEW
Component: User Interface Design → ViewSource
QA Contact: zach → pmac
Comment 17•20 years ago
|
||
This looks like it's a layout bug. The testcase has a <pre> element with a lot
of newlines in it (but nothing under those). View-source is generating the
newlines, but they're simply not being rendered.
Comment 18•20 years ago
|
||
View-source is doing all it can here. The inability to select lines with only a
newline in them is covered by bug 85505. So basically, the moment that bug is
fixed, we can mark this bug as fixed.
Depends on: 85505
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•16 years ago
|
Assignee: doronr → mrbkap
Priority: P4 → --
QA Contact: pmac → doronr
Target Milestone: mozilla1.2alpha → ---
Comment 19•16 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Comment 20•16 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Comment 21•16 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Comment 22•16 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Comment 23•16 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Updated•16 years ago
|
Assignee: mrbkap → nobody
Component: View Source → HTML: Parser
Product: SeaMonkey → Core
QA Contact: doronr → parser
Updated•16 years ago
|
Status: UNCONFIRMED → NEW
Comment 24•16 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Assignee: nobody → mrbkap
Status: NEW → UNCONFIRMED
Component: View Source
Product: SeaMonkey
QA Contact: parser → doronr
Comment 25•16 years ago
|
||
Look. If you don't want this bug in Seamonkey, fine. But then don't move it back in there, dammit!
Assignee: mrbkap → nobody
Status: UNCONFIRMED → NEW
Component: View Source → HTML: Parser
Product: SeaMonkey → Core
QA Contact: doronr → parser
Per comment 18 marking as duplicate of bug 85505.
Status: NEW → RESOLVED
Closed: 24 years ago → 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•