XPost: alt.comp.software.firefox, comp.sys.mac.system   
   From: mariasophia@comprehension.com   
      
   Carlos E. R. wrote:   
   > Using the same selection as in my previous test.   
   > Firefox:   
   >   
   > cer@Laicolasse:~> xclip -selection clipboard -t TARGETS -o   
   > TIMESTAMP   
   > TARGETS   
   > MULTIPLE   
   > SAVE_TARGETS   
   > text/html   
   > text/_moz_htmlcontext   
   > text/_moz_htmlinfo   
   > UTF8_STRING   
   > COMPOUND_TEXT   
   > TEXT   
   > STRING   
   > text/plain;charset=utf-8   
   > text/plain   
   > text/x-moz-url-priv   
   > cer@Laicolasse:~>   
   >   
   > Chrome   
   >   
   > cer@Laicolasse:~> xclip -selection clipboard -t TARGETS -o   
   > TIMESTAMP   
   > TARGETS   
   > SAVE_TARGETS   
   > MULTIPLE   
   > STRING   
   > TEXT   
   > UTF8_STRING   
   > text/plain;charset=utf-8   
   > text/plain   
   > text/html   
   > chromium/x-internal-source-rfh-token   
   > chromium/x-source-url   
   > cer@Laicolasse:~>   
      
   Hi Carlos,   
      
   (I'm going to remove the mac users fu because they're only trolling us.)   
      
   Woo hoo!   
      
   That was WONDERFUL. I love learning how operating systems, um, operate!   
      
   Thank you for investing time and energy into the test.   
    a. Lawrence proved the PSA using wl-paste in Wayland on Linux   
    b. You proved the PSA using xclip in X11 on Linux   
    c. I proved the PSA using InsideClipboard on Windows   
    d. The Apple users are likely way out of their element   
       (In hindsight, I should not have included them as they only trolled.)   
      
   We are all reproducing the PSA exactly as expected.   
   Working together as a team, we are making progress here for everyone.   
      
   Your X11 results line up exactly with what Lawrence demonstrated on Wayland   
   and what I captured on Windows with InsideClipboard.   
      
   Three platforms, three toolchains, and the same pattern every time.   
      
   Firefox exposes text/plain, UTF8_STRING, text/html, and its own Mozilla   
   metadata formats. Chromium exposes text/plain, UTF8_STRING, text/html, and   
   its Chromium-specific metadata formats. The names differ across platforms,   
   but the structure is identical.   
      
   Your X11 TARGETS dump confirms that the clipboard behavior is consistent   
   across Wayland, X11, and Windows. The only thing that changes is how the   
   platform expresses the formats such as   
    a. MIME types on X11/Wayland   
    b. CF_* formats on Windows   
    c. Who knows how macOS does it (least of all the mac users!)   
   The underlying reality is the same on all the tested platforms.   
      
   So yes, you have reproduced Lawrence's Wayland results and my Windows   
   results exactly. This closes the loop and confirms the PSA across all three   
   environments.   
      
   Let me attempt to break down what your X11 output shows, AFAICT,   
   in the same way we analyzed Lawrence's Wayland data and my Windows data.   
      
   FIREFOX ON X11   
   --------------   
   text/html   
   text/_moz_htmlcontext   
   text/_moz_htmlinfo   
   text/plain;charset=utf-8   
   UTF8_STRING   
   COMPOUND_TEXT   
   TEXT   
   STRING   
   text/plain   
   text/x-moz-url-priv   
      
   This matches Lawrence's Wayland results line for line:   
      
    Firefox always exports text/html.   
    Firefox always exports its own Mozilla-specific metadata formats:   
          text/_moz_htmlcontext   
          text/_moz_htmlinfo   
          text/x-moz-url-priv   
    Firefox always exports multiple plain-text formats:   
          UTF8_STRING, TEXT, STRING, text/plain, etc.   
      
   This is exactly what we saw on Wayland, and it is exactly what I saw on   
   Windows (just expressed as CF_* formats instead of MIME types).   
      
   CHROMIUM ON X11   
   ---------------   
   text/html   
   chromium/x-internal-source-rfh-token   
   chromium/x-source-url   
   text/plain;charset=utf-8   
   text/plain   
   UTF8_STRING   
   TEXT   
   STRING   
      
   This is the X11 equivalent of what both Lawrence and I observed:   
      
    Chromium always exports text/html.   
    Chromium always exports its own internal metadata formats:   
          chromium/x-internal-source-rfh-token   
          chromium/x-source-url   
    Chromium always exports multiple plain-text formats.   
      
   On Windows, these appear as:   
          HTML Format   
          Chromium internal source RFH token   
          Chromium internal source URL   
          CF_TEXT   
          CF_OEMTEXT   
          CF_UNICODETEXT   
          CF_LOCALE   
      
   On Wayland, Lawrence saw:   
          text/html   
          chromium/x-source-url   
          chromium/x-internal-source-rfh-token   
          text/plain;charset=utf-8   
          UTF8_STRING   
          TEXT   
          STRING   
      
   Your X11 results match both sets exactly.   
      
   THE CROSS-PLATFORM PATTERN   
   --------------------------   
      
   Across all three environments:   
      
    Firefox exports HTML plus Mozilla metadata plus plain text.   
    Chromium exports HTML plus Chromium metadata plus plain text.   
    The names differ (MIME types on X11/Wayland, CF_* formats on Windows),   
      but the structure is identical.   
      
   This is the key point: Chromium always includes HTML Format and its   
   metadata, even when the selection looks like plain text.   
      
   That is the same behavior that triggered the Windows HTML-to-text   
   conversion bug that corrupted Scintilla's buffer and killed Ctrl+A.   
      
   CONFIRMATION OF THE PSA   
   ------------------------   
    Lawrence confirmed the behavior on Wayland.   
    I confirmed the behavior on Windows.   
    You have now confirmed the behavior on X11.   
      
   Three platforms, three toolchains, one consistent truth:   
      
   Chromium always places HTML Format and internal metadata on the clipboard,   
   and that HTML fragment can influence how downstream applications interpret   
   the plain text.   
      
   This is exactly the Chromium side of the PSA, now verified independently on   
   all major desktop environments.   
      
   Beautiful work, Carlos. Lawrence. Paul. Andy. And others.   
   All of us provided facts that had to be fit into Occam's Razor.   
      
   I'm not sure if this is a bug, but at least we can begin to understand it.   
   --   
   My brain is wired for Occam's Razor, but to be always 100% logically   
   correct, I need to have as many facts as I can to fit into the picture.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)