Content bug: mention since which Firefox version, cookies have SameSite set to Lax by default

[baptx]

What page(s) did you find the problem on?

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite
https://github.com/mdn/content/blob/main/files/en-us/web/http/headers/set-cookie/samesite/index.md

Specific page section or heading?

In "browser compatibility" section, the version number should be added in the row "Defaults to
Lax":
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite#browser_compatibility

What is the problem?

The documentation says "Standards related to the Cookie SameSite attribute recently changed" but it is not mentioned since which Firefox version, cookies have SameSite set to Lax by default, there is just the opt-in mentioned since version 69.
Another problem is that if JavaScript is disabled, for example with an addon like uMatrix or NoScript, the "browser compatibility" section does not load and displays "BCD tables only load in the browser". This error message is not clear enough, it should say "enable JavaScript to view data" but a better solution would be to use progressive enhancement for better accessibility, so we can see the version numbers without JavaScript (there is no need for JavaScript to see text content like version numbers).

Update: it looks like Firefox does not yet default to Lax but we can keep this issue open (and maybe rename the title) to make the "browser compatibility" section work without JavaScript with progressive enhancement or with a fallback at least.

What did you expect to see?

Correct version numbers displayed even if JavaScript is disabled.

Did you test this? If so, how?

Yes, visit the links shared above.

[hamishwillee]

The original problem described is not a bug. What you mean by the suggestion to "without JavaScript with progressive enhancement or with a fallback at least." isn't clear to me. Can you please either clarify, or perhaps create a PR which addresses the issue you see?

[baptx]

@hamishwillee basically with progressive enhancement we will have an HTML table like this:

<table>
	<tr>
		<td>A</td>
		<td>B</td>
		<td>C</td>
	</tr>
	<tr>
		<td>1</td>
		<td>2</td>
		<td>3</td>
	</tr>
</table>

And then then we can add CSS or JavaScript to improve the user experience if necessary.
If this is not possible due to the use of a third-party library for example, we can use a fallback (which is less nice but works) by displaying the HTML table in a <noscript></noscript> tag. The fallback table will then only be displayed in case JavaScript is disabled, for example with the NoScript addon. I noticed that noscript tags currently don't work anymore with uMatrix addon, even with the Spoof <noscript> tags switch enabled (it used to work like described on gorhill/uMatrix#319 (comment) after my issue gorhill/uMatrix#855).
The progressive enhancement solution will have the advantage to work even if noscript tags are not supported and will avoid data duplication by having a separate fallback table.

I don't know if I can update the code myself with a PR but if you have a link to the code used to load the table, I can have a look.

[hamishwillee]

Ah, now I understand you. I'm closing this and have posted as an "infrastructure" issue: mdn/yari#4581