01:37:07 I think I am indeed gonna abandon the xpfe emulated toolbar grippys 01:51:06 what do you think tomman 01:51:16 least you aren't a commie like _nuke 01:58:08 njsg: I seriously don't think anyone would miss em 01:58:59 least the per-toolbar customization isn't tied to it.. I do need to standardize them and perhaps add the methods to the bindings or a jsm or something 01:59:17 man.. will the toolkit even be reconizable once i am done lol? 01:59:32 well consistancy sure ain't a thing in the mozsphere 03:19:56 how do you feel about it IanN_Away 03:20:00 IanN[m]: 03:20:30 conceptually i mean.. not having the toolbar grippys 03:20:35 at all 05:28:11 i don't use them but there are some people that do 05:32:16 toolbargrippy {display: none !important;} probably the first userChrome.css I ever used :) 05:32:32 CaptainTobin: ^ 05:34:28 a-865: well frg added a pref 05:34:33 a-865: they're hidden as default anyway but I think CaptainTobin is talking about removing the code that supports them 05:34:37 i am just gonna ditch the binding 05:35:17 I mean I love them but the actual impl hasn't ever been as easy to maintain as the xpfe binding 05:50:28 I've been using that CSS since somewhere around the turn of the century, whenever Mozilla first showed up on OS/2 05:51:03 good riddance to grippies 05:52:05 some accidental hotkey strike would make things disappear without knowing how to recover :( 05:52:40 Is the pref in the pref panel? 05:52:48 yes 05:52:56 yes, under appearance 05:53:16 soic 05:53:36 :) 06:31:17 http://personal.mattatobin.com/image/capture/23baeba1-b9d8-4671-9dec-72010c8808ce.jpg 06:31:28 there we go IanN_Away a-865 njsg 06:32:22 the xpfe emulated grippy toolbar shit is gone I also removed the last component bar icon and moved the new inline customizable toolbar to the end of the status bar ordinal enforced.. tho i had to set a higher ordinal for the statusbar resizer in the binding 06:32:26 but no biggy 06:33:20 small toolbar mode with text on the size is now the default 06:33:46 I think visually.. it is quite ready to launch but shellservice needs finished 06:35:11 I think it looks very nice in its native windows look 06:35:46 i will have to reinstall an 8.1 and 7 vm to do some spot checks make sure my changes haven't caused a style regression 06:38:02 I dunno if i am gonna keep the netscape 7 new tab text label but i find it fun that just adding the attr had it show up styled exactly right 07:49:07 frg_away: If I were to prep a build vm a vmware vm for you do you think you could poke at trying to get nss past my brickwall at some point 10:06:56 NewTobinParadigm I finally found some time yesterday to check nss and nspr dependencies. This is basically all needed. 1769627-102a.patch is optional and a few others too to make later ones apply clean(er) 10:06:58 series file excerpt: https://paste.debian.net/1255019/ 10:06:59 https://gitlab.com/frg/seamonkey-253-patches/-/commit/4cb15cdb07dbed1cf8d72605bcae70839135db28 10:07:01 Build is stable for a week now including mail and I don't think anything left lurking in the shadows here. ymmv. 10:07:02 nss and nspr are unmodified 1:1 copies. Just still compiling the old dbm module for migrations from pre 2.53.1 10:12:09 The grippie disable pref is not set in release builds as default. Just in the prereleases. In release builds you need to set it one time. I frequently misclicked and did hide the menu or a toolbar and I wasn't alone so it got added. I don't use them but as IanN_Away stated they probably still have a few fans left and we try not to do a mozilla with ui features. Does not mean they won't be... 10:12:11 ...chopped one day or that the ui stays unchanged :) 15:31:09 frg_Away: yeah for 56 but 52-base still can't get past what 3.64 i said? 15:31:44 i was just thinking if i prepped a windows build env and prepped it for building maybe you could see what i see 15:32:21 gonna set up a build vm for your base as well 15:32:42 a build vm or a vhd for native boot 15:33:00 CaptainTobin I am totally swamped. Could take a look at the build log if you have one. I really have use for a clone or two of me :) 15:33:53 i can do a build log but it will be a bit i'd have to lay down the newer version and make mods 15:35:10 i haven't messed with it since april 15:35:24 so obviously it isn't super duper critical 15:35:25 heh 15:36:02 but i also kinda promised to do some work for you guys and maybe i should actually do it at some point? 15:36:16 remember the non-fxa infected weave backend 15:41:50 I'll file a proper bug in a few days but what I plan to do once I get a build env for seamonkey is to first port the tycho weave backend do any settling in adjustments then we will upgrade the bits and make a toolkit sync client fe/be and just have seamonkey provide the couple of bits specific to it while the majority of the component is contained.. chrome addresses are easily overridden not to immidiately break themes 15:46:04 CaptainTobin having sync running would be cool. I am not sure if ewong has the time to set up a server but at least anyone could set up a private one. 15:47:42 well once it is working again then you guys can decide if you are gonna provide a small server for the few hundread that actually can still be bothered to care about what they are using BUT if you do I and my users get to use it for continued maintaince of the component remember? 15:48:28 hell i'd likely still do it anyway i just might not be AS nice about it LOL 15:49:55 https://code.binaryoutcast.com/projects/aura-central/commits/TRUNK/components/weave 15:52:51 check out that tree much cleaner than it was before i dealt with it 15:54:00 of course you note the classic as fuck heirarchy but i suppose you'll want your skin and locale files in their central-ish locations ;) 18:56:09 odd, Palefill suddenly stopped working 18:56:25 at first I thought "oh no, what new Chromeism had the GitHubs and GitLabs deployed this week!?" 18:56:43 tried updating the addon (there was an update released last week), but nothing 18:56:58 the console was giving the dreaded "window.customElements is undefined" crapola 18:57:28 then I decided to restart SeaMonkey and that magically fixed everything! (although the old process hung after closing all windows, so I had to SIGTERM it)