home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   alt.os.linux      Getting to be as bloated as Windows!      107,822 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 107,812 of 107,822   
   Maria Sophia to All   
   Re: PSA: Clipboard differences between C   
   15 Feb 26 22:44:41   
   
   XPost: alt.comp.software.firefox, comp.sys.mac.system   
   From: mariasophia@comprehension.com   
      
   Lawrence D˘Oliveiro wrote:   
   > On Sun, 15 Feb 2026 21:58:46 -0500, Maria Sophia wrote:   
   >   
   >>    Is that a bug?   
   >   
   > Only happens under Windows?   
   >   
   > Probably.   
      
   Hi Lawrence,   
      
   That's a good point because we got so wrapped up in proving that the   
   underlying mechanism were the same between the various platforms (although   
   the mac users only trolled us so I'm gonna remove them in the fup line)   
   that we forget that there is a real "issue" with the Control+A breaking.   
      
   It does seem to be a Windows corruption of Scintilla's internal indexing   
   tables when Windows hands Chromium data to Scintilla.   
    a. line boundaries   
    b. document length   
    c. byte offsets   
    d. character offset   
      
   But why doesn't it happen with Firefox?   
      
   The more confused I am, the more I learn, so I think it all comes down to   
   how each browser constructs its clipboard data diffferently.   
      
   Which, after all, is the SUBJECT line of this thread, as it's all about   
   Firefox versus Chromium, which are on "all common consumer platforms". :)   
      
   Back to Firefox, my tentative assessment is Chromium always puts a full   
   HTML Fragment block on the clipboard, complete with StartHTML, EndHTML,   
   StartFragment, EndFragment offsets, and its own chromium/x-* metadata.   
      
   Yet Firefox does not.   
      
   Unfortunately, Windows uses that HTML Fragment to generate CF_UNICODETEXT.   
      
   If the HTML fragment or offsets are malformed, Windows produces a   
   corrupted CF_UNICODETEXT stream. That corrupted stream breaks Scintilla.   
      
   I can only assume Firefox's HTML fragment is simpler and hence Firefox's   
   HTML fragment does not trigger the buggy Windows conversion path.   
      
   What do you think of that hypothesis of why only Chromium, not Firefox?   
   --   
   This is getting more and more like Heisenberg's uncertainty principle.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca