Ticket #1390 (closed enhancement: worksforme)
Empty values should be consistent across config methods
| Reported by: | pablo | Owned by: | pablo |
|---|---|---|---|
| Priority: | Normal | Milestone: | Player 6.0 beta |
| Component: | flash | Keywords: | |
| Cc: | Forum thread: | http://www.longtailvideo.com/support/forums/jw-player/player-development-and-customization/20468/bug-empty-xml-flashvar-tags-return-zero-0-value-instead-of-undefined-in-56-player |
Description
In Flash plugins, different configuration methods can result in different types of values when retrieving plugin config options, especially when dealing with null values. The player should attempt to normalize the type of returned in these scenarios.
From DaveH:
Just to clarify, the return value from get config calls (eg; player.config('tag')) on an
empty xml flashvar tag (eg; <tag></tag>), in:
* pre-5.4 (cannot recall which version) returns 'null'
* 5.4 & 5.5 returns 'undefined'
* 5.6 returns '0'
* 5.7 returns '' (empty string)
It would be good to define the behavior all across the player so it is always handled the
same way in flashvars (for both XML and flashvar object parameters) and with playlists.
Change History
Note: See
TracTickets for help on using
tickets.

Let's investigate this for the next major player update; we can make sure from the start that the player's config values are consistent.