00:36:37 one of my banks is inviting me to their newest and greatest online banking experience, so it means they paid some interns for more Javascript? 00:36:45 I'll shot myself on the foot, so I'll check... 00:37:46 ...and I'm already getting Javascript exceptions 00:37:48 YAY 00:39:05 they're using ES5 polyfills. yay? 00:40:45 "TypeError: t.toElement is undefined" - of course, it's a bank and a pile of minified JS, but I don't see breakages so far (they're running "the new experience" as a very functionality-limited beta, THANFKULLY) 00:40:59 I guess I'm keeping this bank... for now 00:41:48 (the bank in question is https://www.mercantilbanco.com/ - expect bug reports in the future from me) 00:42:20 ...the very same bank that still uses 32-bit W7 for running some ancient Win16 (yes - 16-bit!!!) app for their backend 00:44:00 instead of fixing their broken ATMs, they invest money in more Javascript bloat :/ 00:44:10 MY money! 01:04:39 but why 01:04:50 why do they need new javascript shinies for? 01:04:58 so they can fuck themselves harder over? 05:52:31 What's the secret to getting the inspector to inspect chrome? Since upgrade from 2.49.5 to 2.53.8.1, tab text is microscopic and I can't ID elements that need userChrome.css adjusted. 05:54:13 a-865: start DOMi, File -> Inspect Chrome Document -> select the window you want to inspect 05:57:32 IanN_Away: thx. Didn't know there remained the ability to have a separate inspector window different from Ctrl-Shift-I :) 05:59:34 How do I get rid of the mailnews window tab bar? X buttons don't. 05:59:55 a-865: yes, in 2.53.x for Debugger's inspector you have to click on the settings cog, scroll down to advanced settings and check the box that says "Enable browser chrome and add-on debugging toolboxes" 06:01:46 I already had done that. 06:02:13 a-865: hmmm, that used to work, seems something might be broken 06:03:56 frg might know more 06:04:51 I already fixed the microtext. On first pass through userChrome.css I missed the most important instance of mozmm to change. 06:06:20 mail window default content text size shrunk massively, much smaller than pref size for monospace. 06:07:37 that mailnews tab bar is irritating 06:07:51 big space waster 06:09:22 a-865: Preferences -> Browser -> Tabbed Browsing -> Hide the tab bar when only one tab is open? 06:11:56 I thought that was for the browser window only, and that it was already enabled. I was wrong about both. :P 06:12:45 a-865: I'll have to see if it is possible to have a separate pref for mailnews 06:17:31 I think I had it enabled and the upgrade switched it off. I don't remember having seen the tab bar in a freshly opened browser window like I commonly open for a screenshot. Otherwise there are always lots of open tabs in browser. 06:18:10 a-865: I think the default changed from 2.49.x to 2.53.x 06:20:12 big disappointment losing mozmm 06:21:03 have to keep old browser around to use pt text sizes in HTML docs 06:23:37 Pale Moon covers it so far 06:27:10 i'd have to lookup what mozmm is about, I presume it was a Mozilla only "standard" 06:47:49 IanN_Away: mozmm in FF versions 4-59 according to https://developer.mozilla.org/en-US/docs/Web/CSS/length note. It was real life size mm when DPI was accurate. 06:48:10 useful substitute for hijacked pt unit 06:53:01 https://bugzilla.mozilla.org/show_bug.cgi?id=1416564 :( 06:56:25 What build do I need to enjoy the Bug 1720003 fix? 06:59:08 I thought I had heard it was already available. :( 07:01:20 browser.tabs.loadDivertedInBackground does nothing in 2.53.8.1 :( 07:06:43 The mailnews reply date is fsck*d up in 2.53.8.1 07:13:23 how do I get the ISO date into the reply header? LC_TIME=en_DK no longer works 07:25:16 the relnote is wrong 09:08:43 ah, the libicu locale dates 09:08:58 now if it were as easy to hack these as it is to modify a glibc locale 09:09:25 last I checked it didn't look like it was an easy endeavour, but I should check it again sometime 09:10:16 a-865: were you using that before or you're trying it for the first time? you may need to toggle one of the locale/i18n settings 11:16:35 IanN_Away If the browser toolbox is available and remote debugging checked it should allow chrome debugging. With toggle tools you can bring up the developer tools too. There is some non working stuff like developer toolbar and responsive design view but older errors. We need to overhaul how the menu is tacked to tools. 11:17:56 a-865: you're opening the browser toolbox, not the "regular" devtools toolbox/inspector? 11:21:07 njsg no chrome debugging is not possible there 11:21:20 It needs a separate remote connection. 13:00:57 clarify needs the browser toolbox. 13:03:42 a-865 Bug 1720003 is only in 2.53.9b1 pre yet. But will not appear in the official 2.53.9b1 and moves to 2.53.10b1. Needs a bit more testing. 14:21:04 njsg: been using en_DK since forever. Dates other than iso are stupid. 14:22:29 I haven't yet tried to change the date format for ICU tools, for everything else the glibc hacks have served me well so far 14:23:33 but I should indeed try to change this here. I'd usually go with ISO 8601 for the date+time format 14:28:55 njsg: toggle locale/i18n setting where? All else but LC_TIME=en_DK is either en_US or blank/default. 14:41:03 in preferences "Appearance", "Date and time formatting", that's already set for en_DK? 14:41:06 a-865: ^ 14:47:47 njsg: it was. I already reverted to 2.49 for my email profile. For the one running CZ (this) it wasn't but is now. Is there a way to test without opening email? 14:48:42 I see it's bad in history window. 14:50:47 In the appearance select list there is only English (United Sta... 15:00:40 if I build the glibc en_DK UTF-8 locale and use it in LC_TIME, the date+time format changes in the list of messages 15:01:04 even if that setting I just mentioned is still set to "application locale" 15:01:21 the "regional settings locale" does show the "English (Denmark)", though 15:01:57 now I still don't get ISO8601, I get four-digit year in D/M/Y and 24-hour time with a dot separator 15:05:09 so just to rule one thing out: is en_DK in the output of "locale -a"? If it's just en_DK.utf8 or en_DK.UTF-8 are you including that (with the .utf/UTF... part) in LC_TIME? 15:08:25 en_DK, en_DK.utf8, en_US, en_US.iso885915, en_US.utf8 15:09:43 set | grep TIME, LC_TIME=en_DK 15:09:59 I took all platform fixes I found for locale display but I won't rule out problems. Totally changed in gecko 55 and 56 was the first version where it was barely usable so I had to backport a bunch of stuff. In Winodws it is fine now if you pick os locale but never got into linux formatting. 15:10:43 a-865: what format are you getting, just the US one with AM/PM and M/D/Y? or something else? 15:11:47 njsg: in history window it's 24 hour time with d/m/y 15:12:52 njsg: LC_TIME=en_DK.utf8 is needed??? 15:14:37 set also includes _=LC_TIME 15:20:29 changing from application to regional (en_DK) in appearance had no effect in history window 15:20:38 a-865: I think if it shows that date format, then it is already picking up en_DK, so that's probably not the problem; I'm wondering if there was a change in ICU 15:23:17 my .bashrc incluces #export LC_TIME=en_DK.utf8 and export LC_TIME=en_DK 15:24:47 looks like it was 2009 when I tried export LC_TIME=en_DK.utf8 15:25:57 (or possibly not ICU, but CLDR) 15:30:12 so far I couldn't find a change in mozilla-central that explains this, the file there has had dd/MM/y only 15:30:33 a-865: which version were you using when this gave you ISO8601? 15:32:21 a-865: if it was 2.49.x (I think you mentioned this earlier today), this might actually be ICU+CLDR vs. glibc 15:32:32 glibc still has ISO8601 for en_DK, here I have 15:32:46 date_fmt "%Y-%m-%dT%T %Z" 15:32:51 d_fmt "%Y-%m-%d" 15:33:25 and so on, in /usr/share/i18n/locales/en_DK 15:35:05 but for icu, intl/icu/source/data/locales/en_DK.txt defines "dd/MM/y" and other day-month-year format strings 15:36:50 I forgot the thunderbird bug was actually about en_DK not working, bug 1426907 15:40:41 with sv_SE, I need to change to regional settings 15:41:01 Bug 1409158 is in. Bug 1337069 give more hints. 15:42:33 Bug 1426907 is not in but I can take a look if it would fix it. 15:43:18 I think I recall something about using the regional setting if the language is the same 15:43:45 (which would explain why en_DK was used despite the selection being "application locale" but sv_SE wasn't 15:43:59 but I imagine using sv_SE might make swedish strings pop up 15:44:16 njsg: 2.49.5 15:44:16 yeah, just opening page info :-) 15:45:40 (I mean, in page info you see swedish strings; I'm guessing the history will show these too) 15:47:21 a-865: ok, my guess is that you were seeing the glibc locale before