"player.play()" doesn't work on Chrome(v.72). This bug happens on windows7 and Android phone.(I don't know about iOS.)
It works well on other versions.
Is there anyone who knows about this bug?
I ran into the same problem.
Adding allow="autoplay" to my parent iframe fixed it as well
Is your youtube iframe wrapped in another iframe (crossdomain)?
If so then it could be caused by the new user activation api v2 (https://developers.google.com/web/updates/2019/01/user-activation)?
And you can solve the issue by adding the allow="autoplay" attribute to your parent iframe.
It didn't make 100% sense to me at first but it fixed the issue we had.
Related
In a website I am developing, the background image is disappearing in Chrome. It is working fine in Edge and Firefox. I tried it in Another laptop to assure the problem is with Chrome and same in other laptop too. On inspecting, I found that for some unknown reason, Chrome automatically adds a property background-image: none; directly to the element.
See the faulty code here
This overwrites the property and div and makes background none. On disabling this property in inspect tool, the background images appears but refreshing page brings back the problem.
Well, here i have suggestions for you:
Check if any adblocker is working in your chrome or not. If yes, then please remove it, and try again.
Do not run the code at Chrome's incognito
Add the style elements at the head section of your HTML file.
Please let me know if it works or not. Don't hesitate to ask further questions.
I have found the root cause. It was due to an extension. It was not the Ad-Blocker in my case. Removing that extension has solved my problem
My app needs to use iframes to work with third party websites.
One of these websites, has a function that automatically sets its "overflow" to "hidden" when it detects itself being used as an iframe.
Is there a fix to this? I know in general if the iframe is not of same origin I shouldn't be able to change their css.
I would also like to know if there is a good reason to set "overflow: hidden" just because it is used as an iframe...
The app runs only on Samsung devices, using Chrome.
Any help is appreciated. Thanks!
Their is nothing legitimate that you can do to fix this. The content of an iframe is sandboxed from the parent page by the security system in the browser.
As for why they do this, I expect they have another usecase where they find it useful, but it would be better to just turn scrolling off in the iframe element, than use overflow like this.
The website I'm working on has issues with how the text is displayed in Google Chrome. I added text-rendering:geometricprecision to make it look better, but apparently it caused some text rendering bug. See this and this video. Any ideas on what might be wrong?
Adding -webkit-backface-visibility: hidden solved the issue.
I am currently having an issue in chrome with a webpage I am working on. When the page loads, there is an odd space after an inline element.
Usually this would be caused by a margin, or some padding. What is peculiar about this issue though is that it isn't. If I disable a CSS rule then re-enable it, it fixes the issue.
The issue doesn't happen in Firefox, so as far as I know it is chrome specific.
Any help or suggestions would be greatly appreciated.
Screenshot of said issue: http://imgur.com/pIjeXnV,UEPWRiB#0
I've solved this issue by having javascript change the css after a short delay and change it back. This emulates the solution that I mentioned viewing through using the inspector.
Since this is more of a work around than a solution, if anyone has any more information about the issue, feel free to comment.
Thanks.
The position:fixed s works perfectly fine when I do not embed a video from Vimeo. Any one knows why and how to work around it? It never used to be like that, only recently.
Does this question's discussion solve your problem? Mac, safari, background-position:fixed and iframe?
Original poster stated: "I worked around this by detecting Mac/Safari and outputting decreased functionality for the people using that system."
I would recommend implementing separate CSS for whichever browsers are causing the issue. Can you provide more details about the problem?