Closed Bug 261498 Opened 20 years ago Closed 19 years ago

CSS interpreter produces invalid borders and scaling

Categories

(Core Graveyard :: GFX: Gtk, defect)

x86
Linux
defect
Not set
major

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: eesterle, Assigned: blizzard)

References

()

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040924
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040924

This CSS bug viewable here:
http://cme.geneticsolutions.com/db/servlet/TopicReq?id=2152

Happens in Mozilla 1.7.3 running on Gentoo 2004.2 and Fedora Core 1 Linux with
"--enable-xft" configure option set.  With "--disble-xft" the CSS appears
correctly.  This used to happen on Windows 98/200/XP in browser version 1.6, but
was fixed in 1.7+, the bug still exists in Linux though. 

Reproducible: Always
Steps to Reproduce:
1. Make sure you use Mozilla 1.7.x with XFT fonts
2. Browse to http://cme.geneticsolutions.com/db/servlet/TopicReq?id=2152
3. Compare the rendered page to the same page opened without XFT fonts, or with
Mozilla 1.7+ on Windows.

Actual Results:  
The border images are not spaced correctly and some sections are not displayed
at all.

Expected Results:  
Rendered all borders consistently and fluint with no apparent sectional spacing.

-. Default theme used.
-. Browser didn't crash
-. Computers discovered on Dell Poweredge 400SC Intel P4 2.4 - 3 GHz, 
-. The CSS on this page was validated by w3c's CSS validator and the section
that displays the borders was validated successfully.

about:buildconfig
------------------
--enable-optimize=-O2 --enable-old-abi-compat-wrappers --disable-activex
--disable-activex-scripting --disable-installer --disable-pedantic
--enable-crypto --enable-mathml --enable-xterm-updates --with-pthreads
--with-system-jpeg --with-system-png --with-system-zlib --with-x
--without-system-nspr --disable-ipv6 --disable-ldap --disable-ldap-experimental
--enable-xinerama --enable-xprint --enable-gnomevfs
--enable-default-toolkit=gtk2 --disable-debug --disable-tests --enable-reorder
--enable-strip --enable-strip-libs --enable-elf-dynstr-gc --enable-xft
--enable-freetype2 --enable-freetypetest --disable-jsd --disable-xpctools
--enable-oji --disable-calendar --disable-svg
--enable-extensions=default,gnomevfs --prefix=/usr/lib/mozilla
--with-default-mozilla-five-home=/usr/lib/mozilla
*** Bug 261499 has been marked as a duplicate of this bug. ***
XFT bug ==> over to blizzard.
Assignee: adamlock → blizzard
Component: Embedding: APIs → GFX: Gtk
QA Contact: ian
Not a Mozilla CSS/XFT bug.  This turned out to be a result of an improperly
formatted table image and CSS implimentation.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Resolution: EXPIRED → INVALID
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.