Skip to main content

Bug Tracker

Side navigation

#6531 closed bug (patchwelcome)

Opened May 05, 2010 04:45PM UTC

Closed June 09, 2011 04:12PM UTC

bind() does not work for QuickTime Plugin Events with 1.4.2

Reported by: gawelt Owned by:
Priority: low Milestone:
Component: data Version: 1.4.2
Keywords: Cc:
Blocked by: Blocking:

bind() does not work for QuickTime Plugin Events.

It works properly with 1.3.2.

problem probably concerns all "banned noData elements".

see line 1586 to 1590.

Attachments (0)
Change History (5)

Changed October 10, 2010 02:02AM UTC by addyosmani comment:1

priority: → undecided
resolution: → invalid
status: newclosed

Closing due to lack of a valid test case. Please re-submit your ticket with a valid test case that we can investigate and inform us what browser you are experiencing the mentioned behavior in.

Changed June 09, 2011 02:54PM UTC by comment:2

Changed June 09, 2011 03:12PM UTC by comment:3

Here is my example in jsFiddle.

Changed June 09, 2011 04:09PM UTC by dmethvin comment:4

milestone: 1.4.2
resolution: invalid
status: closedreopened

Changed June 09, 2011 04:12PM UTC by dmethvin comment:5

component: eventdata
priority: undecidedlow
resolution: → patchwelcome
status: reopenedclosed

gawelt's analysis is correct, we don't allow data to be set on objects or embeds because it crashes several browsers to do that. If you could create a test case that showed it is safe to set a property on QuickTime plugin embeds/objects across IE 6/7/8/9, Firefox 3/4, Chrome, and Opera, we might be able to whitelist it as we did for Flash.