bugzilla.mozilla.org will be intermittently unavailable on Saturday, March 24th, from 16:00 until 20:00 UTC.



9 years ago
8 years ago


(Reporter: cthomasjacobs, Unassigned)


Firefox Tracking Flags

(Not tracked)


(Whiteboard: [CLOSEME 2010-11-01], URL)



9 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_4_11; en) AppleWebKit/525.27.1 (KHTML, like Gecko) Version/3.2.1 Safari/525.27.1
Build Identifier: Firefox 3.0.10

I use yahoo site solutions through Firefox to build my website.

Once I upgraded to 3.0.10, I now have format errors on my website.  Text that appears aligned in Firefox, is not aligned in any other browser, including all versions of IE & Safari (on either Window or Mac platforms).  The text is aligned when viewed through Firefox on a Mac.

Reproducible: Always

Steps to Reproduce:
1. Create a webpage through yahoo small business Site Solutions.  
2. Use spacebar and tab to create two columns of text.  Far left text is aligned (words at the beginning of the line).  then align words in middle of line.
3. save and publish.
Actual Results:  
some text not aligned.

Expected Results:  
all text should be aligned as I designed it on my Site Solutions page.

510-206-1970 (c) for contact information to help solve.
This is a mass search for bugs which are in the Firefox General component, are
UNCO, have not been changed for 500 days and have an unspecified version. 

Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.
Whiteboard: [CLOSEME 2010-11-01]
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 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.
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.