272910 - Right edge / border of active tabs sometimes renders incorrectly

Status: RESOLVED FIXED

(Firefox :: Tabbed Browser, defect)

Description

[Francis Botero]

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

The right edge border of the active tab is being cut off. This only occurs with
a certin number of tabs though. Also the spacing between two tabs, seems to be
off by one or two pixels to the right of the offending tab.
I am using 1024x768 screen resolution with firefox maximized and 6 tabs opened.
I have supplied a gif file at
http://www.crashedweb.com/frankie/firefox/bugs/firefox_bug.gif that shows the
bug as I am seeing it.

Reproducible: Always
Steps to Reproduce:
1. Set screen resolution to 1024x768
2. Maximize Firefox
3. Open Six tabs
4. Click on the second or fourth tab

Actual Results:  
Right border of tab is not being displayed

Expected Results:  
Right border be displayed as in the rest of the tabs

Im using the default theme that came with FireFox 1.0

Comment 1

[Francis Botero]

Attachment: Image of the problem(s)

Comment 2

[Ravenous Bugblatter Beast]

I can reproduce this using today's trunk build. 

As I change the width of the browser window the spacing between tabs varies
between 0 and 2 pixels as they change width. When at zero pixels the right edge
of the active tab isn't drawn correctly.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6) Gecko/20041219
Firefox/1.0+

Comment 3

[C Shoemaker]

Using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317
Firefox/1.0.2 , right borders of 2nd and 4th tabs render incorrectly when 5 tabs
are in use.

Comment 4

[Nathan Ollerenshaw]

Hey guys, this is still happening, on all the platforms - Mac/Linux/Windows.

Any chance of it being fixed? Its a really small issue but its been hanging
around for like, 9 months now.

Comment 5

[Francis Botero]

Looks like this is no longer an issue in version 2.0.0.1