[wp-trac] [WordPress Trac] #27437: UX for Audio/Video/Playlists
WordPress Trac
noreply at wordpress.org
Sun Mar 16 20:48:59 UTC 2014
#27437: UX for Audio/Video/Playlists
----------------------------+-------------------------
Reporter: wonderboymusic | Owner:
Type: defect (bug) | Status: new
Priority: high | Milestone: 3.9
Component: Media | Version: trunk
Severity: blocker | Keywords: needs-patch
Focuses: |
----------------------------+-------------------------
Issues that were brought to my attention:
**Issue No. 1**
Hide "Create Audio|Video Playlist" until you have actually uploaded
Audio/Video files. (I am on it code-wise).
**Issue No. 2**
"Add Audio|Video Source" is super-confusing if you don't understand why it
is there. It is NOT there to create a playlist. It is there to add extra
`<source>` tags to a lone `<audio|video>` tag. More sources = more native
HTML5 playback across browsers. The browser wars are not over, my friends.
Every browser implements their support for audio and video differently.
MediaElement levels the playing field considerably, but HTML5 playback is
always preferable over playback via a Flash or Silverlight bridge. The UI
I have created allows you to accomplish this and edit every aspect of your
shortcode in the media modal.
Is this too much power? Is it too confusing? How can we simplify this?
gcorne already suggested making "Add Audio|Video Source" a button instead
of a prominent nav item.
Playlists are a completely separate thing. "Insert Media" is the launching
point for "Create Audio|Video Playlist". Clicking an audio|video shortcode
placeholder launches "Audio|Video Details." Clicking a playlist shortcode
launches the Playlist editor.
To review: "Image Details" = One Image. Gallery = many images.
"Audio|Video Details" = One Audio|Video, potentially with fallback
sources. Playlists = many audio or video files (no fallbacks).
**Issue 3**
Placeholders/previews for Audio/Video/Playlist shortcodes in TinyMCE.
Working its way over on #27389 and #27320, but related to UX. What is the
best experience here?
The reason I ask: some audio and video formats are better suited than
others to be preview-able in the editor. Namely, all of those sources
which are supported by the browser natively for playback. The
Flash/Silverlight plugins used by MediaElement get weird with TinyMCE.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/27437>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list