Bug 219539

Summary: Epiphany cannot display this webpage containing a video
Product: WebKit Reporter: Frédéric Parrenin <frederic.parrenin>
Component: WebKitGTKAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: aperez, bugs-noreply, webkit-bug-importer
Priority: P2    
Version: Other   
Hardware: PC   
OS: Linux   

Frédéric Parrenin
Reported 2020-12-04 06:33:02 PST
Steps to reproduce: - open Epiphany on Linux (tested on Debian 11 Bullseye) - go to this webpage: https://www.lesnumeriques.com/ordinateur-portable/apple-macbook-pro-13-2020-m1-p60875/test.html - scroll down to the video => The following message appears: "Oups! An error occurred when displaying this page..."
Attachments
Adrian Perez
Comment 1 2021-05-27 11:40:14 PDT
(In reply to Frédéric Parrenin from comment #0) > Steps to reproduce: > - open Epiphany on Linux (tested on Debian 11 Bullseye) > - go to this webpage: > https://www.lesnumeriques.com/ordinateur-portable/apple-macbook-pro-13-2020- > m1-p60875/test.html > - scroll down to the video > => The following message appears: "Oups! An error occurred when displaying > this page..." Hi! I re-tested this with Epiphany 40.1 and WebKitGTK 2.32.1 and the video plays fine for me. Could you check on your end with a newer WebKitGTK version and confirm whether it works now for you? And thanks for the bug report!
Frédéric Parrenin
Comment 2 2021-05-27 12:21:47 PDT
Thank you for your message. I have tested with the version of Epiphany installed on Debian 11, and now it works. Now sure if the webpage is the same as before, though. So I think you can close this bug report.
Adrian Perez
Comment 3 2021-05-27 13:34:02 PDT
(In reply to Frédéric Parrenin from comment #2) > Thank you for your message. > I have tested with the version of Epiphany installed on Debian 11, and now > it works. > Now sure if the webpage is the same as before, though. > So I think you can close this bug report. While the page might have changed, I suspect that the round of multimedia playback improvements we got into the 2.32.x releases may have helped here, too. At any rate, thanks for confirming, and let's close this :)
Note You need to log in before you can comment on or make changes to this bug.