Closed
Bug 752242
Opened 13 years ago
Closed 12 years ago
Gawker Media sites have floating icons in header
Categories
(Web Compatibility :: Site Reports, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: jfu, Unassigned)
References
()
Details
(Whiteboard: [Engagement] [PMM])
Attachments
(2 files)
screenshot
Web page or screen you were on when you saw the issue: m.gizmodo.com/5907887
Steps to reproduce:
1. go to native Twitter app
2. tap on a link from Gizmodo Twitter post
3. End up on m.gizmodo.com/5907887
What you expected: A nice looking mobile optimized site; most of the page looked good, except at the top where a facebook icon is duplicated and hanging in the middle of the page
Not sure if this is Evangelism
Crash report ID (if applicable):
|
||
Comment 1•13 years ago
|
||
I see varying content between Gecko and WebKit
|
|
||
Updated•13 years ago
|
Summary: Floating icons in header of website → Floating icons in header of mobile engadget
|
|
||
Updated•13 years ago
|
Summary: Floating icons in header of mobile engadget → Floating icons in header of mobile gizmodo
|
||
Comment 2•13 years ago
|
||
Yeah, I believe this is evangelism. I see the same thing on Fennec as I do on desktop FF with the fennec UA string, so it's not a fennec-specific bug. Their CSS in general seems to have a bunch of webkit-specific stuff and so doesn't render well in FF.
Component: General → Evangelism
QA Contact: general → evangelism
|
|
||
Updated•13 years ago
|
Summary: Floating icons in header of mobile gizmodo → Gawker Media sites have floating icons in header
|
||
Updated•13 years ago
|
Component: Evangelism → Mobile
Product: Firefox for Android → Tech Evangelism
Version: Trunk → unspecified
|
|
||
Comment 4•12 years ago
|
||
I think this works now. Can't find the problem..
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
|
Assignee | |
Updated•7 years ago
|
Product: Tech Evangelism → Web Compatibility
|
|
Assignee | |
Updated•2 years ago
|
Component: Mobile → Site Reports
You need to log in
before you can comment on or make changes to this bug.
Description
•