Opened 13 years ago
Closed 12 years ago
#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: | ||
| Blocked by: | Blocking: |
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 (5)
comment:1 Changed 13 years ago by
| Priority: | → undecided |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
comment:2 Changed 12 years ago by
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:4 Changed 12 years ago by
| Milestone: | 1.4.2 |
|---|---|
| Resolution: | invalid |
| Status: | closed → reopened |
comment:5 Changed 12 years ago by
| Component: | event → data |
|---|---|
| Priority: | undecided → low |
| Resolution: | → patchwelcome |
| Status: | reopened → closed |
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.
Note: See
TracTickets for help on using
tickets.
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.