Hacker Read

spydum · 2014-04-08 16:44:30

You cannot override "Use compatibility mode for all sites". It's a master switch. No X-UA-Compatible header, No meta tag, and no DOCTYPE will save you from this scourge.

bartlomieju | karma 240 | avg karma 5.22 · | 2022-08-15 09:21:40

"compat" mode has been supported for some months now: https://deno.land/manual/node/compatibility_mode

Jasper_ | karma 10186 | avg karma 5.95 · | 2022-10-25 14:05:57

Probably worth pointing out that while this will appear to work, it's certainly not ICCCM [0] compatible, so a lot of toolkits and applications that assume ICCCM compatibility will break.

[0] https://www.x.org/releases/current/doc/xorg-docs/icccm/icccm... , one of the standards for how WMs and X11 applications should communicate.

reply

quambene | karma 73 | avg karma 1.16 · | 2024-01-05 20:00:59

isn't supported anymore?

scrollaway | karma 28520 | avg karma 4.25 · | 2015-08-07 23:26:29+00:00

It's not supported.

ComputerGuru | karma 29702 | avg karma 4.11 · | 2020-05-21 07:08:51+00:00

Yeah, but that’s not the issue/question. Not supporting webp is fine, the important thing is that it doesn’t send an accept header that includes it. I don’t believe it does.

bscphil | karma 8137 | avg karma 3.41 · | 2019-09-11 04:34:08

It doesn't support these at my institution. Maybe they haven't rolled out this version? (Technically you can get U2F to work, but they have a bright red warning that says it's unsupported when you do that.)

petepete | karma 6750 | avg karma 3.41 · | 2023-03-10 02:48:05

This is probably a good case for a compatibility mode where these APIs are enabled.

kianworkk | karma 38 | avg karma 1.81 · | 2024-06-10 02:04:22

I meant that it is not supported yet. I will add this to the to-do list, and I believe it does not conflict with the goals of SiteProfile. Thank you for your feedback.

invalidname | karma 1659 | avg karma 1.82 · | 2022-06-25 04:22:10

All of them support canonical links. So no.

Pxtl | karma 17051 | avg karma 3.07 · | 2016-08-26 12:25:50+00:00

That still seems overly specific in that the content server must opt-in by using nosniff, but I guess that's the reality of backwards-compatibility.

Sk1pp | karma 17 | avg karma 1.0 · | 2016-11-17 15:40:54+00:00

I only see it supporting yahoo. I didn't try very hard but in the settings there is no way to change it from yahoo, which is really frustrating. Did I overlook something?

david_ar | karma 319 | avg karma 2.49 · | 2015-10-29 05:50:30+00:00

Is there a particular reason why it's not supported?

flyheart | karma 1 | avg karma 1.0 · | 2013-03-21 09:50:59

not supported

dagmx | karma 11637 | avg karma 4.02 · | 2024-01-20 18:49:43

Ah interesting. Trying to find documentation led me to believe it’s still unsupported but guess not.

Either way, I think it’s on Meta to do some of the legwork to land third parties.

reply

Jaruzel | karma 11536 | avg karma 4.55 · | 2018-03-13 19:09:50+00:00

Unless of course, you are running Exchange. In which case it's not supported :(

malkia | karma 4426 | avg karma 1.58 · | 2022-01-18 19:43:02

re: compatibility. There are some guides to pervent compatibility issues - https://developers.google.com/protocol-buffers/docs/proto3#u...

crazygringo | karma 69969 | avg karma 7.48 · | 2021-05-02 21:33:48

Not all webservers support/enable it, so YMMV.

But as long as you're dealing with a known server that does, then gravy!

reply

rdpintqogeogsaa | karma 5514 | avg karma 16.03 · | 2021-11-21 02:19:50

I'll take this opportunity to point out that Ed25519 support is an open issue, but no one has stepped up to specify it yet.[0]

[0] https://github.com/httpwg/http-extensions/issues/1509

reply

Can_Not | karma 985 | avg karma 0.81 · | 2019-03-09 14:02:43+00:00

It's a supported client but not a supported host.