Getting this error in Safari, but other browsers work fine.

Question

Getting this error in Safari, but other browsers work fine.

delta0800 opened this issue 5 years ago · comments

Andrew · Answer 1 · Sun Dec 08 2019 19:43:33 GMT+0800 (China Standard Time)

@delta0800, Thanks. I have researched a little but haven't find out a proper solution 😢. But your issue gave me the idea of creating a prop named iframeAttributes, which will apply the value of that prop to the <iframe /> element, so we can set any <iframe /> attribute we want.

Andrew · Answer 2 · Sun Dec 08 2019 19:49:30 GMT+0800 (China Standard Time)

Added ability so set custom <iframe /> attributes: 1ee83c4. I am going to release a new minor version ASAP.

delta0800 · Answer 3 · Sun Dec 08 2019 22:00:01 GMT+0800 (China Standard Time)

Hi Andrew, How are you? Thanks for the quick response and effort. I will give a try later to resolve the iframe issue. Have a nice day. Thanks Lawrence

…

Sent from my iPhone

On 8 Dec 2019, at 19:49, Andrew ***@***.***> wrote: Added ability so set custom <iframe /> attributes: 1ee83c4. I am going to release a new minor version ASAP. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

Andrew · Answer 4 · Mon Dec 09 2019 04:33:06 GMT+0800 (China Standard Time)

@delta0800, I have noticed that YouTube gives you an <iframe /> element which have attribute allow, set to accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture. I have also updated the value of the allow attribute to match the YouTube version. See 9c2e4ce.

delta0800 · Answer 5 · Mon Dec 09 2019 16:49:16 GMT+0800 (China Standard Time)

Hello Andrew, I saw that the new update with the allow attribute same as YouTube. Last night I tried to run npm update for the package somehow it still the old version contents. But I checked in package.json Have updated to 1.2.2 Any advise? Please correct me if any silly mistakes I have made. Hope I can learn more from you. Thanks Lawrence

…

Sent from my iPhone

On 9 Dec 2019, at 04:33, Andrew ***@***.***> wrote: @delta0800, I have noticed that YouTube gives you an <iframe /> element which have attribute allow, set to accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture. I have also updated the value of the allow attribute to match the YouTube version. See 9c2e4ce. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

Andrew · Answer 6 · Mon Dec 09 2019 17:52:52 GMT+0800 (China Standard Time)

@delta0800, I have released a beta version. It's being tested right now, becaise as for now I am not sure it's stable. You can install a beta version running this command:

npm i vue-lazy-youtube-video@1.3.0-beta.0

I will publish a stable 1.3.0 realese as soon as I am sure everything works properly.

Andrew · Answer 7 · Mon Dec 09 2019 19:11:04 GMT+0800 (China Standard Time)

@delta0800, Actually there is no need for it. New version 1.3.0-beta.1 with SSR support is released.

delta0800 · Answer 8 · Tue Dec 10 2019 20:14:27 GMT+0800 (China Standard Time)

Hello Andrew, Thanks for the email. Noted that. Have the issue resolve at your end? I will try tonight version 1.3.0 . The error message at safari actually is about the Allow attributes in iframe in my understanding. For the new release have you resolved it at your end? Thanks Lawrence

…

Sent from my iPhone

On 9 Dec 2019, at 19:11, Andrew ***@***.***> wrote: @delta0800, Actually there is no need for it. New version 1.3.0-beta.1 with SSR support is released. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

delta0800 · Answer 9 · Tue Dec 10 2019 22:30:14 GMT+0800 (China Standard Time)

Hello Andrew, How are you today? I have updated the package to the latest release. I still got the message without correct 'allow' attribute. Maybe i have made some mistake. Below are screenshot of my template. View blade

…

On Dec 9, 2019, at 6:11 PM, Andrew ***@***.***> wrote: @delta0800 <https://github.com/delta0800>, Actually there is no need for it. New version 1.3.0-beta.1 with SSR support is released. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#6?email_source=notifications&email_token=AMVYSCUWWIZJIA2WXY25NM3QXYRUTA5CNFSM4JW4EUU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGIY5FQ#issuecomment-563187350>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMVYSCRNU7CHLPEWPLARDGLQXYRUTANCNFSM4JW4EUUQ>.

Andrew · Answer 10 · Wed Dec 11 2019 02:11:47 GMT+0800 (China Standard Time)

@delta0800, Sorry but still I do not know hove to solve this issue? Are you running your code on site with HTTPS protocol?

delta0800 · Answer 11 · Sat Dec 14 2019 12:39:50 GMT+0800 (China Standard Time)

Hello Andrew, How are you? Today is Sat hope you have a great weekends. Sorry for the late reply this few days. I done some research also from others they have this problem also On Safari. I tried also to run it through https have the same problem too. Just to make sure with you there’s no issue with the code I write right? I will keep on trying if I have find the answer I will email you too. Wish you have a nice day. Thanks Lawrence

…

Sent from my iPhone

On 11 Dec 2019, at 02:11, Andrew ***@***.***> wrote: @delta0800, Sorry but still I do not know hove to solve this issue? Are you running your code on site with HTTPS protocol? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

Andrew · Answer 12 · Thu Jan 02 2020 23:01:03 GMT+0800 (China Standard Time)

@delta0800, Thanks a lot!

delta0800 · Answer 13 · Fri Jan 03 2020 00:38:57 GMT+0800 (China Standard Time)

Happy New Year to you @andrew. Welcome 2020! Cheers !

…

Sent from my iPhone

On 2 Jan 2020, at 23:01, Andrew ***@***.***> wrote: @delta0800, Thanks a lot! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

Andrew · Answer 14 · Sat Mar 07 2020 19:03:06 GMT+0800 (China Standard Time)

@delta0800, Do not getting this issue anymore.

delta0800 · Answer 15 · Sat Mar 07 2020 21:32:15 GMT+0800 (China Standard Time)

Hello Sir, How are you? Hope you are fine. I am glad to hear that it’s fixed. I will check it. Thanks Lawrence

…

Sent from my iPhone

On 7 Mar 2020, at 19:03, Andrew ***@***.***> wrote: @delta0800, Do not getting this issue anymore. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.