02:36:24 found this today on HN: https://jamesl.me/atto/ 02:36:31 of course, it doesn't work on Seamonkey 02:37:01 doesn't exactly tell what Google-esque features it requires, it just redirects me to https://jamesl.me/atto/notsupported.html 02:37:46 oh, it says something about "lookbehind in regex" not working on Apple toys, maybe it's the same on SM? 02:41:09 yup, the check is very simple: https://jamesl.me/atto/supportcheck.js 02:41:28 regex stuff, which curiously also fails on Safari 02:43:36 (hence the authors' rant, for which no other browsers exist but Chrome, "recent Firefox", and Safari because iPhones) 06:20:52 bug 1225665? 06:24:06 ah, yes, it's linked from the webkit issue linked on the notsupported page 06:24:25 «Considering that all modern browsers -- save for Safari/WebKit -- support regex lookbehind» 06:24:43 * njsg wonders how many are "all modern browsers"... 11:39:12 njsg atto = yapl it seems. And the site is something you can pass all day without missing a thing so no loss. Another form over function. 20:47:30 njsg: tomman: lookbehind issue seems to be fixed by bug 1634135. A lot of commits, but kinda new subdir mostly -- let's hope it won't be that hard to backport... 21:12:50 buc they imported the complete regexp parser from Chrome. This is not the hard part but integrating with Spidermonkey. I looked at it a few months ago when some other site broke. Possibly 100 to 200 patches and for the last part not easy ones. 21:17:23 wait, what?! 21:17:30 now Mozilla is borrowing code from Chrome, wow 21:18:25 tomman. Wonder when they will import V8 and call it a day :) 21:19:00 that reminds me. new month so need to check statcounter. 21:21:18 Down again: https://gs.statcounter.com/browser-market-share/desktop/worldwide?desktop-browser-ww-monthly-202001-202107# 21:21:20 Not much but the trend is your friend... But next month when the Photon theme is becoming such a hit after all the naysayers have quit it will be huuuge!!! 21:21:27 speaking of regex stuff, remember those sites with broken OpenWeb comment forms? 21:21:33 like Simple Flying, among others 21:21:46 those have never worked since they went full-Chrome 21:22:08 but now, I get a different error: "SyntaxError: invalid regexp group" 21:22:58 it's on a bunch of minified JS from launcher.spot.im, lovely 21:24:17 well with basically one regexp parser having 99% merket share I bet testing is done widespread across browsers :) 21:24:49 ironically it's only Apple users that dare complaining... at Apple! 21:25:17 maybe Webkit/Safari should stagnate on purpose, if only to put a reality check on Google 21:25:42 noone cares about us, but if it is the browser on America's most loved cellphone, maybe things would change 21:39:08 I'm playing with mail "Archive" issue, bug 1718839. After applying the patch, no more errors in console. And even a new per-year subdir is created under "Archives" folder. That's all. Nothing else changed -- the mail remains in Inbox... 21:40:08 The same scenario with 2.53.7.1 works fine. 21:44:33 Could anybody confirm that mail "Archive" works as expected after applying the first patch from bug 1718839 (note it is applicable against omni.ja)? 22:07:57 buc you need both. It creates the folder but then hits the second error with the missing function. 22:20:38 frg: Hmm... Some empty-like mail is received, seems from you... 22:24:36 and yes, the second patch helps :) 22:33:11 buc nope didn't sent it. Spammer of the day maybe. 22:38:28 To add to it the removed function was also used for drag and drop. I never realized because the patch in Bug 515675 takes care of this. So ther might be d&d breakage too in 2.53.8. 22:43:09 Well, seems another issue -- when I playing with moving a mail between archive and other folders, sometimes the mail "disappeared", and a broken mail (headers only, even partial) with some garbage data (from old already removed messages) appeared instead. 22:53:35 This is not different from moving regular mail around. I have yet to see this but you never know. This is all new code and might still have bugs. 23:00:05 Would it be suitable for downstream level to revert (for a while) the changes from bug 1694760? Ie. do not "Switch to MailServices in Message Display code" for a one release cycle? 23:15:50 This is a bunch of bugs Main one was Bug 507601. I would not touch it. Overall it it stable or one of us whould have hit the problems sooner and I and also IanN_Away too would rather have testers. The old code had just different problems and they were harder to fix. 23:35:28 In ~50% cases when moving a mail from the local "Archive-->2021" folder "back" to the Inbox folder on an Imap server, the "local copy" of the Inbox's mail appears broken. (Some garbage fragment, kinda partial headers from a previously received mail etc.) The copy on the imap server remains valid. 23:37:19 Probably removing the "2021" subfolder and/or unexpand the "Local Folders" help to trigger the issue. Still cannot find 100% reproducible case... 23:55:17 Well, steps to reproduce: 23:55:17 send you an email to be appeared at imap server; 23:55:17 remove "ImapMail/" and "Mail/" directories from your profile; 23:55:17 start "seamonkey -mail", see your test mail; 23:55:17 "Archive" the mail, it then appears in "Local Folders-->Archives-->2021"; 23:55:17 move the mail from this 2021 back to the Imap Inbox; 23:55:18 try to see it again there. It is broken now. 23:57:11 The copy on server remains OK. If you remove ImapMail/ and start again, you will see it is not corrupted.