274591 - opacity with float value causes rogue horizontal lines

Status: RESOLVED INVALID

(Core :: Layout, defect)

Description

[Phil Webb]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.5) Gecko/20041110 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.5) Gecko/20041110 Firefox/1.0

Setting opacity to some value other than 1 or 0 causes additional horizontal
lines to appear a fixed distance below the tag whose transparency is being
altered. Occurs only with complex table structures. I'm unable to produce a
simple example to demonstrate this.

opacity: 1 is ok
opacity: 0 is ok
opacity: 0.6 is not
opacity: .6 is not

See uploaded png for example of the output. The transparent row is that with the
text 'Something'

Reproducible: Always

Comment 1

[Phil Webb]

Attachment: Screenshot of problem

Comment 2

[Phil Ringnalda (:philor)]

Unfortunately, without a URL or a testcase, even a complex one, the odds of
anyone looking at it (unless they recognize it as a dup) are not at all good.
Since there were tons of fixes to Gecko between when Firefox 1.0 branched and
now, the first thought anyone involved in layout will have is "is this already
fixed?".

Comment 3

[Boris Zbarsky [:bzbarsky]]

Phil, can you please attach an HTML page showing the problem?  And as Phil
Ringnalda said, could you please test a current trunk build?

Comment 4

[Phil Webb]

As previously stated, and I realise this makes it difficult to repro, I've not
been able to produce a sample page that demonstrates this - the pages that I saw
this on *were* on our proprietary intranet which I can't give you (annoyingly) -
however I was able to workaround by dropping hidden DIVs from within TDs.

I'll try it on current trunk build asap.

Comment 5

[Karl Johan Kleist]

Maybe related to bug 281953? which I just filed.

Comment 6

[Gervase Markham [:gerv]]

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/

Comment 7

[Peter van der Woude [:Peter6]]

no response by submitter
->INVA