Closed Bug 783245 Opened 12 years ago Closed 12 years ago

Error: TypeError: this.obj.SetVariable is not a function

Categories

(Core Graveyard :: Plug-ins, defect)

Product:
Core Graveyard
Component:
Plug-ins
Platform:
x86
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: alex_mayorga, Unassigned)

References

(
URL
)

Details

Steps:
1. Load http://ww2.noticiasmvs.com/entrevistas/primera-emision-con-carmen-aristegui/postura-de-mvs-sobre-rescate-banda-25-ghz-conferencia-de-prensa-139.html
2. Click the gray/blue play button

Result:
No audio plays and this error appears in "Error Console":

    Error: TypeError: this.obj.SetVariable is not a function
    Source File: http://184.173.72.162/js/unified.js?ver=1.1.22
    Line: 810

Expected result:
Audio plays

Workaround:
Use IE

Initially reported to http://forums.mozillazine.org/viewtopic.php?p=12201989#p12201989 with a confirmation from another user at http://forums.mozillazine.org/viewtopic.php?p=12202535#p12202535
The problem reproduces even in safe mode.
I'm not able to reproduce the bug with Nightly on Win 7.
Strange, I get it every time on Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:17.0) Gecko/17.0 Firefox/17.0 ID:20120815101724
And with a new profile?
No, but I've pinned it down to plugins.click_to_play;true
Blocks: click-to-play
The issue is with click-to-play. With plugins.click_to_play = true, audio controls like sound level are missing. Activating plugins by clicking on the icon in the location bar doesn't fix the issue, the user needs to reload the page to display correctly Flash elements like the audio player.
Component: Untriaged → Plug-ins
Product: Firefox → Core
If a webpage assumes that they can script a plugin immediately after creating the <object> or <embed> tag, then of course they are going to have issues. This is an inherent problem, not something we can really fix.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
(In reply to Benjamin Smedberg  [:bsmedberg] from comment #6)
> If a webpage assumes that they can script a plugin immediately after
> creating the <object> or <embed> tag, then of course they are going to have
> issues. This is an inherent problem, not something we can really fix.

Should it be turned it into a "Tech Evangelism" bug perhaps?
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.