hi,

I've noticed a minor code redundancy when using the Spotify embed block in the EasyBlog editor. The generated <iframe> code includes both the legacy allowfullscreen attribute and the modern allow="... fullscreen ..." attribute at the same time.

The Observation (Console Warning): Because of this redundancy, modern browsers like Chrome output the following warning in the developer console: Allow attribute will take precedence over 'allowfullscreen'.

Here is the exact HTML output generated by the EasyBlog block:

<iframe style="border-radius: 12px" width="100%" height="152" title="Spotify Embed: [Title]" frameborder="0" allowfullscreen allow="autoplay; clipboard-write; encrypted-media; fullscreen; picture-in-picture" loading="lazy" src="https://support.creative-graphics.ch/..."></iframe>

To clean up the console output for developers and adhere to modern HTML standards, I suggest removing the standalone allowfullscreen attribute from the iframe templates of media blocks (such as Spotify, YouTube, etc.), as the allow attribute already handles the fullscreen permission perfectly.

Thank you!