Ticket #6531 (closed bug: patchwelcome)
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: | ||
| Blocking: | Blocked by: |
Description
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.
Change History
comment:1 Changed 3 years ago by addyosmani
- Priority set to undecided
- Status changed from new to closed
- Resolution set to invalid
comment:2 Changed 2 years ago by darrelkathan@…
I have 2 examples: Working: http://99.23.209.251/dtunes4/jquery_132-quicktime_events_test.html Non-working: http://99.23.209.251/dtunes4/jquery_161-quicktime_events_test.html
comment:3 Changed 2 years ago by darrelkathan@…
Here is my example in jsFiddle. http://jsfiddle.net/mh9vg/
comment:4 Changed 2 years ago by dmethvin
- Status changed from closed to reopened
- Resolution invalid deleted
- Milestone 1.4.2 deleted
comment:5 Changed 2 years ago by dmethvin
- Priority changed from undecided to low
- Resolution set to patchwelcome
- Status changed from reopened to closed
- Component changed from event to data
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.
Please follow the bug reporting guidlines and use jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.
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.