Closed Bug 631720 Opened 13 years ago Closed 2 years ago

If OOPP is disabled then Google Translator can't speak

Categories

(Core :: Layout, defect)

x86
Windows 7
defect
Not set
major

Tracking

()

RESOLVED WORKSFORME
Tracking Status
blocking2.0 --- -

People

(Reporter: .bugzi.lla4tr.ollface, Unassigned)

References

Details

(Keywords: regression)

User-Agent:       Mozilla/5.0 (Windows NT 6.1; rv:2.0b12pre) Gecko/20110204 Firefox/4.0b12pre
Build Identifier: 

Google Translator works only if OOPP is enabled.

Reproducible: Always

Steps to Reproduce:
1. about:config
2. set dom.ipc.plugins.enabled to false
3. go to http://translate.google.com/#auto|en|hello
4. click "Listen" button
Actual Results:  
No sound gets played.

Expected Results:  
Google translate should say "hello".
Confirmed
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b12pre) Gecko/20110204 Firefox/4.0b12pre ID:20110204030345

Regression window:
Works:
http://hg.mozilla.org/mozilla-central/rev/5f0bd7129549
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a1pre) Gecko/20091026
Minefield/3.7a1pre ID:20091026045849
Fails:
http://hg.mozilla.org/mozilla-central/rev/2e01e97f9ded
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a1pre) Gecko/20091027
Minefield/3.7a1pre ID:20091027043823
Pushlog:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=5f0bd7129549&tochange=2e01e97f9ded

In local build,
build from 556728346e52: works
build from c0a5b63c3f3d: fails

WORKAROUND: append the folowing CSS to userContent.css. 
* { opacity:1 !important; }
.
Bug 601064 does not fixed the problem if OOPP is disabled
Blocks: 522394
Status: UNCONFIRMED → NEW
blocking2.0: --- → ?
Component: General → Layout
Ever confirmed: true
Keywords: regression
QA Contact: general → layout
Version: unspecified → Trunk
Blocks: 601064
Error
in local build,
build from 556728346e52:fails
build from c0a5b63c3f3d:  works
Yeah. Are we blocking on bugs where OOPP is disabled?
No, definitely not.
blocking2.0: ? → -

Marking this as Resolved > wfm since I cannot reproduce the issue using the latest Fx versions and the last activity on this issue was 11 years ago. Feel free to re-open if the issue is still reproducible on your end in the latest FF versions.

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