14:35:57 <nsITobin> IanN_Away
14:40:38 <frg_Away> nsITobin hi
14:41:29 <nsITobin> just checking email
14:43:00 <nsITobin> follow up to the match ns*App.cpp for another change.. and IanN_Away needsinfo for a chatzilla patch that seems to clean up and merge a protocol service jsm into the chatzilla regular js comp.. need to do a bit more history checking on it before I chime in on it
14:44:05 <nsITobin> I need a better way to track bugs
14:44:46 <frg_Away> The current cZ will not always close the view whren you leave but that is because of the latrst patch.
14:45:17 <nsITobin> https://wiki.mozilla.org/Bugzilla:REST_API
14:47:22 <nsITobin> frg_Away: how come?
14:48:57 <frg_Away> nsITobin you mean bugzilla usability degration or?
14:49:06 <nsITobin> chatzilla
14:49:30 <nsITobin> has ambassador been harvested for chatzilla advancements btw?
14:49:47 <nsITobin> cause ascrod did work especially on adding more ircv3 bs
14:50:05 <frg_Away> IanN_Away is on it. Bug 1927582 is not 100%
14:53:25 <nsITobin> oh that.. yeah have fun with that
14:55:16 <nsITobin> 1926406 is the one i was feedback?'d on
14:59:42 <nsITobin> and i have to fix 1912354 formatting
15:00:22 <nsITobin> Like I said I need a better way to track bugs lol
15:58:10 <nsITobin> more up to date docuemntation on bugzilla's REST api https://bmo.readthedocs.io/en/latest/api/core/v1/bug.html#get-bug
15:59:25 <nsITobin> so all i need to do is make something that will request a list of bugs and also request extended info on a specific bug to start off simple enough
16:14:24 <tomman> Time to update the nightly here
16:14:44 <tomman> frg_Away: anything hot since "early September builds"?
16:16:06 <frg_Away> tomman sec fixes and a few changes to cZ and places (bookmarks) among other things. Testing appreciated.
16:16:15 <tomman> cool, will do
16:23:19 <frg_Away> cZ might have the mentioned problem when leaving a channel but will be fixed soon. Needs a doiuble close.
16:27:42 <nsITobin> welp my 2014 fm2 computer is dead dead.. can't be revived i think its the motherboard
16:27:59 <nsITobin> well the case makes a half-way decent box to cram books into
16:28:04 <nsITobin> not as efficient as before
16:28:06 <nsITobin> but...
16:44:54 <tomman> testin'~
16:45:35 <tomman> fun, the spacing on the nick list looks extra tight today
17:11:55 <frg_Away> tomman yes changed a bit with the last patch.
18:03:00 <tomman> OK, speaking of that nick list, found something weird
18:03:15 <tomman> after a while, it gets filled with way more nicks than what actually present on a channel
18:07:24 <tomman> yeah, the nick list gets filled with nicks from other channels where I'm currently, not just the current one!
18:07:30 <tomman> that's definitely a first
18:09:37 <tomman> https://news.ycombinator.com/item?id=41976529 in other news, Hackernews has strong opinions about validation in HTML forms
18:10:12 <tomman> they strongly believe that the proper side to do validation is Client Side, using megabytes of JavaScript framenotworks, and of course with unique UI/UX twists
18:12:40 <tomman> OK, the nick list is bugged on all channels I'm on
18:12:54 <tomman> it eventually "merges" all the nick lists for every channel I'm on for no reason
18:13:05 <tomman> it may happen after a few seconds or even minutes
18:36:08 <Sompi> I was told that the Digital and Population Data Services Agency of Finland has a list of "real browsers" that the public sector websites has to be usable with
18:36:22 <Sompi> And apparently browsers that aren't on that list are not "real browsers"
18:36:33 <Sompi> But I don't know the specific, I asked where that list is but no reply
18:36:58 <Sompi> But I understand from this that they are breaking things on purpose
18:37:27 <Sompi> The person who told this works in developing websites for the public sector
18:38:22 <Sompi> And if the page works with those "real browsers", then they conclude that it works on a "wide range of user agents"
18:38:25 <tomman> "Real Browsers"
18:38:34 <Sompi> Yes, that's the wording he used
18:38:40 <tomman> what makes us then, Complex Browsers?
18:42:03 <Sompi> Again about that new version of Finlex, they claim that it "improves accessibility" compared to the old one
18:42:22 <Sompi> The old one works on everything, the new one requires support for the newest JavaScript things to work at all
18:42:59 <Sompi> How can they even say that it makes its accessibility better? IMO the accessibility of the new one is much, much worse...
18:43:23 <Sompi> And that literally happens every time. They always say that the new thing is more accessible, when it's really just the opposite
19:22:49 <nsITobin> I found out what that cord is plugged into LOL
19:22:51 <nsITobin> frg_Away:
19:25:32 <tomman> if I switch channels (tabs), then the nick list correctly repopulates... and eventually gets polluted again with the nick lists from other channels...
19:25:59 <tomman> seems to have even across different networks
19:26:26 <tomman> (I'm connected to Libera and OFTC, and eventually I get every single nick on a single channel, even if said channel has 3 users :D )
19:49:27 <nsITobin> is this still a tree control?
19:49:35 <nsITobin> or the list item view
20:21:03 <frg_Away> nsITobin list view
20:35:28 <nsITobin> if there is some observer firing when the server sends the various channel lists maybe some extra filtering is needed or something.. tho tree views may be automatically instanced or something?
20:36:20 <nsITobin> our tree views are str8 from the heart of the beast they are amazing but difficult to use
20:39:54 <nsITobin> be back