nick

@sp3ctre ich fürchte bei beiden oberes Äffchen.

@firefox @OpticalMoose @pbarker in recent news: https://tilvids.com/videos/watch/76317521-084f-4b17-aef8-94a6d5163c03

#Forefox #Mozilla #Browsers #DontDoThisToMeMozilla #DontDoThisToMeFirefox

@firefox More on #Mozilla in general: https://tube.kockatoo.org/w/cybhHJfhyXmwyED53Sk2F3

#MozillaFoundation #MozillaFinances #Browsers #OpenSource #Video #PeerTubeVideoRecommendation #VideoRecommendation

@OpticalMoose @pbarker
Here are some links:
* VideoEncoderConfigurationPreset of different #Browser​s: https://api-ref.agora.io/en/video-sdk/web/4.x/globals.html#videoencoderconfigurationpreset
* The (arguably or not needed) #CSSContainerStyleQueries comparison: https://caniuse.com/css-container-queries-style
* #WebShareAPI: https://caniuse.com/web-share
* #ViewTransitions: https://caniuse.com/view-transitions
* #JPEGXL(and other #codec integration chart): https://connect.mozilla.org/t5/ideas/support-jpeg-xl/idi-p/18433
* The gradient bug, open since 2011: https://bugzilla.mozilla.org/show_bug.cgi?id=627771

@OpticalMoose that's what I thought, but the CSS and visual/style stuff aside,
* web standard request in #Firefox being undefined("body does not exist")
* Network streamed response only showing up after the response ends
* various video playback restrictions(possibly leaking memory)
but also stuff that wasn't mentioned in the Video like, hardware accaleration issues, old code base or features like HDR not being implemented.
And I'm not even starting with Google being the default search engine..