Closed Bug 231009 Opened 21 years ago Closed 17 years ago

Mozilla needs to make up its mind about how to display an unmapped character entity

Categories

(Core Graveyard :: GFX: Gtk, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: tenthumbs, Assigned: blizzard)

Details

(Keywords: testcase, Whiteboard: CLOSEME 07/01)

Attachments

(4 files)

I have a simple test page which has some unmapped character entities. On initial
load it uses the '?' character which is fine. If I scroll down and then back up,
it decides that it's found a glyph from a font and uses it but does not reformat
the table so the glyph is badly misplaced. If I reload the page, then mozilla
goes back to '?'. If I scroll down and up, mozilla uses the glyph it found but
this time it's laid out properly.

Attachments upcoming.
Attached file test page
Attached image scroll down and up
Assignee: nobody → blizzard
Component: Layout: Fonts and Text → GFX: Gtk
QA Contact: core.layout.fonts-and-text → ian
Blocks: xft_tracking
Keywords: testcase
I can't reproduce the behavior on 1.6 (gtk2 + xft). Is your build an Xft build? 
Neither gtk2 nor Xft, just my own debug trunk build.
Then (if you built your build without Xft enabled), why did you mark this bug as
 blocking bug 172768? Bug 172768 is for Xft-related bug only.  
No longer blocks: xft_tracking
I didn't.

dbaron@dbaron.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|nobody@mozilla.org          |blizzard@mozilla.org
          Component|Layout: Fonts and Text      |GFX: Gtk
          QAContact|core.layout.fonts-and-      |ian@hixie.ch
                   |text@bugs                   |


blizzard@mozilla.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
OtherBugsDependingO|                            |172768
              nThis|                            |
Does this bug still occur in a recent trunk build?
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/
Whiteboard: CLOSEME 07/01
Testcase is WFM, current Firefox trunk on Linux.

-> WORKSFORME
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: