Closed
Bug 292242
Opened 20 years ago
Closed 17 years ago
go.com - Text displayed in disneyworld.disney.go.com appears overlapped
Categories
(Tech Evangelism Graveyard :: English US, defect)
Tech Evangelism Graveyard
English US
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: admin, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Every visit to this page shows text that overlaps each other within a table.
This does not occur in other browsers.
Reproducible: Always
Steps to Reproduce:
1. go to
http://disneyworld.disney.go.com/wdw/resorts/resortOther?id=ResortBenefitsPage#magicalexpress
2. View page
Actual Results:
Text appeared jumbled.
Expected Results:
displayed the text clearly, without overlapping
Updated•20 years ago
|
Assignee: general → nobody
Component: Bugzilla-General → General
Product: Bugzilla → Firefox
QA Contact: default-qa → general
Comment 1•20 years ago
|
||
Bug still present in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2)
Gecko/20050428 Firefox/1.0+
Comment 2•20 years ago
|
||
Component: General → English US
OS: Windows XP → All
Product: Firefox → Tech Evangelism
QA Contact: general → english-us
Hardware: PC → All
Summary: Text displayed in the page appears overlapped → Text displayed in disneyworld.disney.go.com appears overlapped
Updated•19 years ago
|
Assignee: nobody → english-us
Updated•19 years ago
|
Summary: Text displayed in disneyworld.disney.go.com appears overlapped → go.com - Text displayed in disneyworld.disney.go.com appears overlapped
Comment 3•17 years ago
|
||
Looks like Disney changed something, because I don't see any overlapping at all in Camino trunk, Firefox 2, or Safari 3. FIXED, as far as I'm concerned.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•