Comment to 'Plyr: DOM security errors'

Comment to Plyr: DOM security errors

· Billy

· 2024-05-28T12:38:45+0000
I think this is normal 3rd party browser warnings/errors. It's possible UNA could do something, however, it's also possible that this is the future. What I mean is, more and more browsers (especially my favorite, Brave) block 3rd party embeds, scripts, css, etc. Then you will see warnings and errors in your dev console. It happens on my WordPress sites with YouTube embeds. But, I know the YouTube embeds are safe so I ignore it, for now.
- · Wise
  
  · In reply to
  
  Billy
  
  · 2024-05-28T22:31:03+0000
  You are incorrect. As a web developer for 20+ years, and not a script kiddie, having DOM security errors is an ISSUE.
  UNA released Plyr. Therefore this needs fixed by them. I am not spending my time figuring out UNA errors.
  If a browser throws an error, something is wrong. I've reported, no issue tracker.
- · Billy
  
  · In reply to
  
  Wise
  
  · 2024-05-29T04:45:56+0000
  I don't think I'm 100% incorrect, just misunderstood. I didn't want someone like me to come here, read this thread, and think there was a huge security issue with UNA. I think this typically occurs when trying to access or manipulate the CSS rules of a stylesheet that originates from a different domain. Seems like an easy fix for the UNA devs (hopefully). 🤞