Closed
Bug 593660
Opened 15 years ago
Closed 14 years ago
The new "Mark as important" buttons in GMail does not render well
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: vishal.prabhu, Unassigned)
References
()
Details
(Keywords: qawanted)
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:2.0b4) Gecko/20100818 Firefox/4.0b4
Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:2.0b4) Gecko/20100818 Firefox/4.0b4
The new "Mark as important" buttons in GMail does not show up well. The buttons appear larger than the other buttons and the lower border is broken. These buttons appear correctly on Firefox 3.6.8 and Firefox 4.0b4 on Mac.
Reproducible: Always
Steps to Reproduce:
1. Login to GMail
2. Enable the Priority Inbox
Actual Results:
Shown in the attachment
Expected Results:
Shown in the attachement
| Reporter | ||
Comment 1•15 years ago
|
||
| Reporter | ||
Comment 2•15 years ago
|
||
my experience with google properties is that if there's something wrong with them one day, it'll be fixed w/in a week or two. the last time an engineer wanted to "fix" a broken google property (youtube), I told him to wait. he came back to me a few days ago indicating that it wasn't broken anymore.
If you're interested in tracking this down, i'd recommend you use DOM Inspector to make a reduced testcase:
https://developer.mozilla.org/en/Reducing_testcases#Useful_tools
Component: General → Layout
Keywords: qawanted
Product: Firefox → Core
QA Contact: general → layout
Version: unspecified → Trunk
Comment 4•15 years ago
|
||
On Firefox/3.6.9 ID:20100824153629 the "Mark as not Important" Button is 1px too high, too - else okay opposed to Trunk Rendering.
Google Chrome 7.0.514.0 & Opera 10.70.9036 render as expected.
Comment 5•14 years ago
|
||
Do you still see this problem when using current release of firefox?
Whiteboard: [closeme 2011-12-15]
Resolved per whiteboard
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2011-12-15]
You need to log in
before you can comment on or make changes to this bug.
Description
•