bboard

Posted by funkyass
wow, look at all the edge in that chat log.

such angst, so teenager.

Posted by Mei Koyoki

Posted by funkyass
wow, look at all the edge in that chat log.

such angst, so teenager.

guess I should stop hanging around places with actually intelligent and go back to tiktok and tumblr, where I can gloat about my edge and be a whore all day!!!11!1!1!!1

[08:11]   tomman  https://old.reddit.com/r/palemoon/comments/bvf0z4/why_is_pale_moon_forum_so_incredibly_toxic/eps8vwu/ wait, what?
[08:11] tomman  oh man, so many fake news in a single statement
[08:12] tomman  ...or perharps in a single line (the one related to Seamonkey)
[08:30] WG9s    tomman: Yes Tobin's involvement in the SeaMonkey project seems to be confined to trolling here telling people they should be using PaleMoon instead!
[09:52] njsg    And doing anything there probably requires an account
[11:08] frg_away        tomman well he is not involved. For the rest I don't care.

Posted by tomman
MozillaZine[/url], although that place is doomed due to the impending close of the latter (it seems that MZ has been in autopilot lately, with downtimes becoming common).

Posted by "J.J. - GitHub developer support"
... it would be disingenuous of us not to recognise that there is clearly a difference of opinion where our use of custom elements is concerned. GitHub considers this open specification part of a diverse and healthy set of modern web standards. As these standards continue to be adopted and supported by web developers and browser maintainers (Chrome, Firefox, Safari, and Edge), we will continue to make use of them. For browsers {sic: without support for WebComponents} ..., further degradation is a likelihood.

I appreciate that this is disappointing and frustrating for you, as the lead developer of one such browser, but we would like to be upfront and honest about the future implications here.

Posted by Nicholas Steel

The day Giggityhub (and by extension, Microsoft/Google) sent Pale Moon (and by extension, each and every non-Chrome browser that isn't "latest Firefox version") to eat a bag of dicks:

Posted by "J.J. - GitHub developer support"
... I appreciate that this is disappointing and frustrating for you,

WHAT??!?

[11:30]   tomman  https://bugs.chromium.org/p/chromium/issues/list fun, more Google Webcomponents blast! (does not work on Seamonkey)
[11:31] robobox they could have done that in 50 lines of css and another 30 of javascript
[11:31] tomman  Well, I guess I'll add Monorail to my sh*tlist
[11:31] tomman  what's the point of a bugtracker if you can't use it because it's broken?
[11:32] tomman  oh, they have a "View in the old UI" link
[11:32] tomman  ...that it's only a list of projects that redirect you to their borked Webcomponents junk
[11:33] robobox file a bug on monorail
[11:34] tomman  "Monorail supports all browsers defined in the Chrome Ops guidelines."
[11:34] tomman  OK, they do allow to do that
[11:34] tomman  log me with my Google account.... fine
[11:35] robobox I only use those for google mail and youtube (although not much worth watching there execpt music)
[11:35] tomman  https://chromium.googlesource.com/infra/infra/+/master/doc/front_end.md "Chrome, Chredge, whatever browser ships on iDevices because Apple, and I guess latest Firefox"
[11:36] robobox wonder what they say about SM, if anything
[11:36] tomman  lovely, their compatibility list for Monorail is their "Chrome Infrastructure" list, aka what Google cares
[11:36] robobox it seems to work in ESR 78
[11:40] tomman  https://bugs.chromium.org/p/monorail/issues/detail?id=8963 HA! I can't even read my own bug report!
[11:40] tomman  LOVELY
[11:41] tomman  so yeah, I guess I'll stick to Trac for when people ask me for a simple, modern bugtracking solution
[11:42] tomman  I can feel myself channeling my inner jwz

Posted by funkyass
It also doesn't work on FF 60 ESR, which was from 2 years ago, and what Seamonkey is currently based on.

This is like complaining about doom not running on a 286.

Posted by funkyass
Doom required and designed around the memory model of the flat model of 386's protected mode. You could rewite the memory management to work on with 286's PM, but it would be next to unplayable, and you'd need to reboot the machine afterwards.

And the funny thing, support for web components was fully enabled in FF 63, added in FF 59.

does seamonkey's about config have dom.webcomponents.shadowdom.enabled somewhere?

Sorry, this website does require web components support. We aim to support the two latest stable versions of Chrome, Edge, Firefox, and Safari as per our browser support guidelines: https://chromium.googlesource.com/infra/infra/+/master/doc/front_end.md#front_end-development-guidelines