Change of character size when come back from other Tab




Tabbed Browser
10 years ago
8 years ago


(Reporter: Chanur, Unassigned)


Firefox Tracking Flags

(Not tracked)


(Whiteboard: [CLOSEME 2010-11-15])


(1 attachment)



10 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; .NET CLR 3.0.04506)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; fr; rv:1.9) Gecko/2008052906 Firefox/3.0

Change of character size when come back from other Tab

Reproducible: Always

Steps to Reproduce:
1.playing Ogame with personal skin (char size 11 px). or go to a other tab.
3.return to Ogame, using tab
Actual Results:  
The display for char is in 14 px (original CSS of Ogame)

Expected Results:  
Display char in 11 px (size specified in my skin)

Background, color of char are note changed when I come back with Tab.

I have use the "!important" keyword in my CSS, the problem is the same.

Comment 1

10 years ago
Created attachment 329004 [details]
personal file of CSS

Comment 2

10 years ago
It's not a problem of CSS but a problem of resolution :

normal resolution : 1085 * 813

back from other tab : 997 * 732
This bug was reported using Firefox 3.0 or older, which is no longer supported. The bug has also not been changed in over 500 days and is still in UNCO.
Reporter, please retest this bug in Firefox 3.6.10 or later using a fresh profile, If you still see this problem, please update the bug. If you no longer see the bug, please set the resolution to RESOLVED, WORKSFORME.

This is a mass search of unconfirmed bugs that have no activity on them, so if you feel a bug was marked in error, just remove the CLOSEME comment in the whiteboard within the next month.
Whiteboard: [CLOSEME 2010-11-15]
No reply, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile ( 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.