-
tomman
the more I read about window.event, the more I want to rip out my eyes out of its sockets
-
tomman
it's an IE-specific _bug_, yet we got places like Western Digital actively implementing IE-specific _bugs_ IN 2021!!!!
-
tomman
WTF I CAN'T EVEN
-
tomman
-
tomman
and of course, "fixing" that on our browsers risks breaking addons, but that's too much for webdevs to understand :/
-
frg_Away
tomman just a guess that it is window.event. Didn't look at the code.
-
NewTobinParadigm
frg_Away: didn't window.event get revised back out of existance in favor of the shit before?
-
NewTobinParadigm
This feature is no longer recommended. Though some browsers might still support it, it may have already been removed from the relevant web standards, may be in the process of being dropped, or may only be kept for compatibility purposes. Avoid using it, and update existing code if possible; see the compatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.
-
NewTobinParadigm
YEP
-
NewTobinParadigm
So basically Mozilla spent a ridiculous amount of time to convert to top-level ambigous window.event then a few years later.. OOPS nevermind we were just joking!
-
NewTobinParadigm
Glad we never put in the massive effort to do it on UXP
-
NewTobinParadigm
That's the problem with draft specs or chrome-isms as defacto
-
frg_Away
I am quite sure this "great" feature is responsive for some websites breaking like button clicks not being recognized. Maybe even the broken ebay zoom. The mozilla bug liststs a lot of websites and even while older I suspect this list grows now that every "modern" browser supports it.
-
NewTobinParadigm
nearly every "modern" browser is chrome though
-
NewTobinParadigm
or trying to be chrome
-
NewTobinParadigm
IF it IS the reason for the ebay zoom issue.. somehow it is obscured
-
NewTobinParadigm
and the error surpressed
-
NewTobinParadigm
else the consoles would clearly indicate it
-
frg_Away
Seems to me the mouse event never gots thru so might be it. Just a guess again.
-
buc
Strange IMAP INBOX folder duplication.
-
buc
If you remove ImapMail/ subdir (from your profile), on the next mailer start it will be recreated, but INBOX will be placed as ImapMail/<servername>.sbd/INBOX. All the other folders will be in ImapMail/<servername>/ subdir (without .sbd suffix).
-
buc
But after the second start, yet another INBOX will appear now as ImapMail/<servername>/INBOX. (All the same for INBOX.msf too).
-
buc
The imap server is dovecot.
-
buc
Can anybody pls confirm this?
-
buc
2.49.5 behaves the same.
-
buc
If you manually remove this .sbd subdir, all works fine without it. So old existing profiles are not affected...