Tried with default theme:
Tried with all other plugins disabled:
Chrome Version 71.0.3578.98
ARVE Version: 8.10.3 ARVE-Pro Version: 4.2.5 WordPress Version: 5.0.3 PHP Version: 5.6.38 ACTIVE PLUGINS: Advanced Custom Fields: ACF Code Field: 1.7 Advanced Custom Fields PRO: 5.7.10 Advanced Post Manager: 4.4 ARVE Advanced Responsive Video Embedder: 8.10.3 ARVE Pro Addon: 4.2.5 Better Notifications for WordPress: 1.7.2 Login With Ajax: 3.1.7 SSH SFTP Updater Support: 0.7.4 ARVE OPTIONS: bool(false) bool(false) bool(false) ARVE PRO OPTIONS: bool(false)
RE: The “responsive” behavior is not working for the Classic Editor in a Gutenberg WP website.
We are in the process of upgrading our website to Gutenberg and testing all aspects of the website for possible issues from the upgrade, as the website is highly customized and includes a custom theme and many custom data-driven applications.
We use the ACF (Advanced Custom Fields) plugin for adding a vast number of custom fields to native and custom post-types. Many of our custom post-types have the Classic Editor (the pre-Gutenberg WYSIWYG). This editors (from ACF) has been retained by the ACF plugin for the Gutenberg release so it continues to function the same way it did prior to Gutenberg.
We use ARVE for the responsive video. It works fine in the Gutenberg blocks and classic block. But the “responsiveness” of embedded videos do not work in custom fields with the Classic WYSIWYG Editor. Any videos embedded in the Classic Editor (from ACF) stops working under Gutenberg.
We have a copy of the website without the Gutenberg release (to be phased out). The embeds work just fine in our pre-Gutenberg website with ARVE 8.9.7 and ARVE Pro 4.1.0.
Would it be possible to update your plugin so responsiveness function as expected for Classic Editors (i.e. from ACF)?
You should have mentioned the max-width limit of 660px getting applied earlier. That is why I always ask for as much information as possible.
You claimed “the responsive behavior was not working” from what you say now I guess this is a issue a few people are having regarding a new fallback for this I implemented to not make ARVE load HD images on mobiles … my guess is the responsiveness is working just fine its just that it will not get bigger beyond 660px.
ARVE falls back to the $content_width variable of your theme, generally set in functions.php. If your theme has the wrong set by its developer there then this will effect the max-width default of ARVE. If your content area gets bigger then that then go do the ARVE options and set the max-width to the correct value. You can also fix this in the theme itself but if its a auto-updating theme it will be overwritten on next update.
Let me know if this fixes this.