Closed
Bug 172768
(xft_tracking)
Opened 21 years ago
Closed 12 years ago
xft tracking bug
Categories
(Core :: Graphics, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: blizzard, Assigned: blizzard)
References
Details
Hang your xft bugs here!
Assignee | ||
Updated•21 years ago
|
Alias: xft_tracking
Comment 1•21 years ago
|
||
how do I add bugs here ? I wanted to add bug 182878 thanks
Updated•21 years ago
|
Comment 2•21 years ago
|
||
I build mozilla using --enable-xft and I get weird behaviour when scrolling. I have noticed this bug since 1.2. This is on a machine with linux 2.4, xfree86 4.3, gcc 2.95.3 and glibc 2.2.5. I attach all the `configure' parameters I use at the end. First of all, with my xft-enabled builds, I get a blinking cursor everywhere, even if I am not at a text input field. If I press page-down, the behaviour depends on where the blinking cursor is; this is a bit complicated, I 'll try to explain the best that I can. For example, on slashdot there is a short `Sections' column at the left which is shorter than the others. If the blinking cursor is on that, then page down doesn't work correctly; it shows the next page for 0.1 seconds and then returns to the current page. This doesn't happen if I first click on the longer central column somewhere (where the main stories are). I've noticed this problem on all similar pages and I have to use the scroll-bar. Pressing `space' also doesn't do anything, whereas till 1.0.x I always used the space to scroll the page down. I have not build mozilla without xft since 1.0.x, so I am not sure that this is because of --enable-xft. I am just guessing, since apart from `--enable-xft' I use more or less the same configure options since 0.8. Moreover, I've not encountered the problem on other non-xft builds; I don't get any blinking cursor and scrolling works perfectly. The commands that I use in my spec file to build mozilla are: export MOZILLA_OFFICIAL=1 export BUILD_OFFICIAL=1 export MOZ_INTERNAL_LIBART_LGPL=1 ./configure \ --prefix=%{_prefix} \ --mandir=%{_mandir} \ --enable-optimize=-O3 \ --enable-strip-libs \ --enable-nspr-autoconf \ --enable-crypto \ --enable-xft \ --enable-reorder \ --enable-strip \ --enable-elf-dynstr-gc \ --enable-cpp-rtti \ --enable-extensions="all" \ --enable-svg \ --with-system-jpeg \ --with-system-png \ --with-system-mng \ --with-system-zlib \ --disable-debug \ --disable-tests \ --disable-jsd \ --disable-mathml \ --disable-accessibility \ --disable-dtd-debug \ --disable-logging make
What about bug 236739? It seems like regression from bug 197037...
Comment 4•12 years ago
|
||
I am under the impression that Xft has long since been superseded by some combination of freetype, pango, cairo, and harfbuzz. Does it still make sense to keep this bug and/or its dependencies open?
Comment 5•12 years ago
|
||
... also I don't know what it's doing under XUL.
Component: XUL → Graphics
QA Contact: jrgmorrison → thebes
Comment 6•12 years ago
|
||
XFT is no more.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•