doesn't break line (carriage return) after rss-scrolltext

RESOLVED INCOMPLETE

Status

()

RESOLVED INCOMPLETE
11 years ago
8 years ago

People

(Reporter: X2-007, Unassigned)

Tracking

3.0 Branch
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [CLOSEME 2010-07-30], URL)

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9b2) Gecko/2007121120 Firefox/3.0b2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9b2) Gecko/2007121120 Firefox/3.0b2

Firefox 2 makes a linebreak after each RSS-scrolltext and puts the next part of the text into the next line. Firefox 3 beta 2 doesn't make a linebreak after each RSS-scrolltext and puts the next text at the end of the same line.

Reproducible: Always

Steps to Reproduce:
Open URL, wait until all RSS-newsfeeds are loaded
Actual Results:  
The info text about the RSS-source will be shown at the end of the same line as the RSS-newsfeed

Expected Results:  
The info text about the RSS-source should be shown in the next line

Source code:

<script type="text/javascript" src="http://www.rss-source.com/newsfeed.gci?id=12345"></script>
<a href="http://www.rss-source.com/" target="_blank">(rss-source.com)</a><br>
<br>
Moving this bug to the RSS component.
Component: General → RSS Discovery and Preview
QA Contact: general → rss.preview
It's only "the RSS component" if you see Firefox's feed preview page, not in every case where the letters "RSS" appear in the summary.
Component: RSS Discovery and Preview → General
QA Contact: rss.preview → general
Does this happen in firefox 3.6.6 or later in a new profile?
Whiteboard: [CLOSEME 2010-07-30]
Version: unspecified → 3.0 Branch
No reply, INCOMPLETE. Please retest with Firefox 3.6.8 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.