ShortFuse

Windows 10 and it's not a good idea

Upmouse

Don't use JSON for the response unless you include the response header to specify it's application/json. You're better off with regular plaintext unless the request header Accept asked for JSON and you respond with the right header.

That also means you can send a response based on what the request asked for.

403 Forbidden (not Unauthorized) is usually enough most of the time. Most of those errors are not meant for consumption by an application because it's rare for 4xx codes to have a contract. They tend to go to a log and output for human readers later, so I'd lean on text as default.

While

Whyle

Whyull

Yull

Yul

Women are so cute and the best chance I can get the kids to be able to get the kids to be able to get the kids to be able to get the kids to be able to get the kids to be able to get the kids to be able to get the kids to be able to get the kids to be able to get the kids to be able to get the kids to be able to get the kids

This actually propels the plane.

The turbine engines are there to look big and make noise to have the passengers feel safe. Big turbines also allow airlines to charge extra, and generate bigger profits. CO2 emissions are also intentionally raised to justify higher pricing.

Even line-height in CSS3 is draft. Saying no drafts should be implemented is a ridiculous standpoint: a standpoint not even Firefox aligns with:

Standardization requirements for shipping features

What evidence is necessary will vary, but generally this will be:

W3C - the specification is at the Candidate Recommendation maturity level or more advanced; shipping from a Working Draft or a less advanced specification requires evidence of agreement within the working group that shipping is acceptable

https://wiki.mozilla.org/ExposureGuidelines

But keep moving those goal posts.

What? They all have W3C specs. Firefox just chose not to implement them.

• https://www.w3.org/Graphics/Color/Workshop/talks.html
• https://www.w3.org/TR/appmanifest/
• https://wicg.github.io/shape-detection-api/#barcode-detection-api
• https://www.w3.org/TR/nfc/
• https://www.w3.org/TR/accname-1.2/#computation-steps
• https://drafts.fxtf.org/css-masking/#the-mask-border

You think you're trashing Chrome, but you're trashing Firefox instead.

Firefox, unfortunately, has been lagging behind. Safari is close to surpassing Firefox if they haven't already. Safari really made a big shift for actually implementing web standards around 16.4.

• No HDR - relevant for me because I mod PC games for HDR
• Dropped PWA on desktop - even Apple went full 180° and embraced it now on Mac OS X. Chrome really gets a good push from this from Microsoft constantly helping push more app manifest stuff since it appears one of their goals is to render more things over Edge PWAs (eg: like the title bar), and resort less to having to use electron.
• No masked borders - can't do custom element borders like corner cutting or perfect squircles. Rounded edges only

Chrome is still the absolute best for accessibility. Neither Firefox nor Safari properly parse the aria labels when it comes to how things are rendered. Chrome will actually render text in accessibility nodes as presented on screen (ie: with spacing). Safari and Firefox only use .textContent which can have words beingmergedwhentheyshouldn't.

Chrome also has Barcode and NFC scanning built right in. I've had to use fake keyboard emulators for iOS. Though, Chrome on Mac OS X also supports it. Safari has native support for Barcode behind a flag, so it'll likely come in the future. Barcode scanning is still possible with Firefox through direct reading of the camera bitmap, which is slower but still good. There's no solution for NFC for Safari, but if Chrome ever comes iOS, that would possibly be solved. I believe Face Detection is similar, but I've never used it.

STD: site-transferred data

Something something ground loop detection, maybe.