Context Navigation

Changes between Initial Version and Version 4 of Ticket #51417

Ticket #51417
- Property Keywords needs-patch added
- Property Milestone changed from Awaiting Review to Future Release

-                      initial
+                      v4
 Hi,
 We have new, way more efficient graphic formats coming - avif and webp. They are already supported by Firefox and Chrome. The recommended and backwards compatible method of inserting them is using a picture tag with an img fallback, for example:
   <picture>
   <source srcset="example.avif" type="image/avif">
   <source srcset="fallback.webp" type="image/webp">
   <img src="fallback.jpg" alt="AVIF example with WebP and JPEG fallback">
   </picture>
+{{{
+<picture>
+<source srcset="example.avif" type="image/avif">
+<source srcset="fallback.webp" type="image/webp">
+<img src="fallback.jpg" alt="AVIF example with WebP and JPEG fallback">
+</picture>
+}}}
 Using the filter tiny_mce_before_init I can make TinyMCE accept the code if it is not surrounded by caption shortcode. Unfortunately the editor handles the [caption] code in javascript, the file is wp-includes/js/tinymce/plugins/wpeditimage/plugin.js
 and it has a filter:
                         img = c.match( /((?:<a [^>]+>)?<img [^>]+>(?:<\/a>)?)([\s\S]*)/i );
+{{{
+img = c.match( /((?:<a [^>]+>)?<img [^>]+>(?:<\/a>)?)([\s\S]*)/i );
+}}}
 which removes everything except a and img tags. So <picture> and <source> become stripped. There is no filter nor configuration to modify how that JS works.