Note: There are a few cases of duplicates in user autocompletion which are being worked on.

Scribd pages displayed with missing content on the latest trunk (position:absolute combined with -moz-transform:scale)

RESOLVED FIXED in mozilla10



Layout: Block and Inline
6 years ago
6 years ago


(Reporter: George Carstoiu, Assigned: Ehsan)


({regression, testcase})

regression, testcase
Dependency tree / graph
Bug Flags:
in-testsuite +

Firefox Tracking Flags



(Whiteboard: [fixed by bug 656875], URL)


(2 attachments)



6 years ago
Mozilla/5.0 (Windows NT 5.1; rv:10.0a1) Gecko/20111001 Firefox/10.0a1

When viewing Scribd document, its content is not displayed, although it works correctly on other browsers.

Reproducible: always

Steps to reproduce:
 1. Go to
 2. Observe document (compare with other browsers)

Actual results:
 - the content is not displayed

Expected results:
 - the content is displayed 

 - issue is reproducible also on a clean profile
 - issue not reproducible on Firefox 7 - Mozilla/5.0 (Windows NT 5.1; rv:7.0) Gecko/20100101 Firefox/7.0

Comment 1

6 years ago
Regression range:

Last good nightly: 2011-09-29
First bad nightly: 2011-09-30


good: f96e4ff817a7  bad: 49b3a14730de
Severity: normal → major
Component: General → Layout
Keywords: regression, testcase-wanted
OS: Windows XP → All
Product: Firefox → Core
QA Contact: general → layout
Hardware: x86 → All
Created attachment 564055 [details]
Testcase #1

Opera and Chrome renders this the same as Firefox used to, fwiw.
Blocks: 10209
Component: Layout → Layout: Block and Inline
Keywords: testcase-wanted → testcase
QA Contact: layout → layout.block-and-inline
Summary: Scribd pages displayed with missing content on the latest trunk → Scribd pages displayed with missing content on the latest trunk (position:absolute combined with -moz-transform:scale)
Blocks: 691166
tracking-firefox10: --- → ?
I guess this is Ehsan's, but you can take it Mats if you want to.
Assignee: nobody → ehsan
Argh, I bet this is the same problem as bug 656875.  I backed out that patch when I backed out bug 10209 the first time, but among the tens of patches which I was keeping around, that patch got lost.  I'm trying a local build to see if reapplying that patch fixes this problem.
Yes, this is indeed fixed by the patch in bug 656875, which I've just pushed to inbound.

I'll keep this open to add a test based on the attached testcase.
Depends on: 656875
Whiteboard: [will be fixed by bug 656875]
Created attachment 564393 [details] [diff] [review]
Attachment #564393 - Flags: review?(roc)
Attachment #564393 - Flags: review?(roc) → review+
Flags: in-testsuite+
Whiteboard: [will be fixed by bug 656875] → [fixed by bug 656875]
Target Milestone: --- → mozilla10
Last Resolved: 6 years ago
Resolution: --- → FIXED


6 years ago
tracking-firefox10: ? → -
You need to log in before you can comment on or make changes to this bug.