Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Media component with HTML5 Player #105

Closed
cagataycivici opened this issue Apr 19, 2015 · 8 comments · Fixed by #6547
Closed

Media component with HTML5 Player #105

cagataycivici opened this issue Apr 19, 2015 · 8 comments · Fixed by #6547
Assignees
Milestone

Comments

@cagataycivici
Copy link
Member

Consider using HTML5 player with Media component

@justin-wesley
Copy link

I would consider raising the priority on this since most modern browsers support this and with the security concerns surrounding Flash, more organizations are dumping the use of Flash.

@markusg80
Copy link

In my opinion use of flash is death and if you add html5 media support Primefaces will be unbeatable framework also for the future! See also my request #1193

@tandraschko
Copy link
Member

@Rapster "object" has been chosen as "video" was likely not available at this time. The component is quite old and never got a facelift.
So if you have ideas and time to work on, feel free.

@Rapster
Copy link
Member

Rapster commented Mar 12, 2017

We should discuss what media should support, same as today (audio, video and PDF)? Is it some sort of delegator, encoding the right HTML5 component depending the input?

See https://www.w3schools.com/html/html_media.asp

@tandraschko
Copy link
Member

I think we just should decide somewhere if object or video is rendered. Maybe it can be handled via type or we need a new flag.

@melloware
Copy link
Member

melloware commented Jul 1, 2020

@tandraschko @Rapster i think with the recent spat of problems both reported and in the forums with the Media player I think we should create two new components p:audio and p:video that do the equivalent of each HTML5 tag and that way its not 1 component trying to do everything. The <audio> and <video> tags have different properties anyway so i doesn't make sense to mix them.

Then the old PDF functionality doesn't even seems like it works anymore anyway. Thoughts?

@markusg80
Copy link

+1

1 similar comment
@tandraschko
Copy link
Member

+1

@melloware melloware self-assigned this Nov 23, 2020
@melloware melloware added this to the 9.0 milestone Nov 23, 2020
@melloware melloware linked a pull request Nov 23, 2020 that will close this issue
melloware added a commit that referenced this issue Nov 26, 2020
* Fix #105, #6545, #6546: HTML5 Audio and Video components

* Fix #105, #6545, #6546: HTML5 Audio and Video components

* Fix #105, #6545, #6546: HTML5 Audio and Video components
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants