FF135 Certificate Transparency

[hamishwillee]

FF135 provides support Certificate Transparency. This adds a release note and minor updates to the CT doc.

Fixes #35570

Related docs work can be tracked in #37811

[github-actions]

Preview URLs

• /en-US/docs/Mozilla/Firefox/Releases/135
• /en-US/docs/Web/Security/Certificate_Transparency

External URLs (3)

URL: /en-US/docs/Mozilla/Firefox/Releases/135
Title: Firefox 135 for developers

• https://bugzil.la/1938242 (2 times) (Note! This may be a new URL 👀)

---

URL: /en-US/docs/Web/Security/Certificate_Transparency
Title: Certificate Transparency

• https://googlechrome.github.io/CertificateTransparency/log_policy.html (1 time) (Note! This may be a new URL 👀)
• https://support.apple.com/en-us/103703 (1 time) (Note! This may be a new URL 👀)

(comment last updated: 2025-01-27 00:08:18)

[hamishwillee]

This bit fixes #35570 by noting the spec things are implemented on and the current version.
Note, I'd do this with spec-urls metadata but they shows unknown specs for both.
I'm also in discussion with BCD team about whether the version data can go into BCD, which IMO would be better.

[bsmth]

whether the version data can go into BCD, which IMO would be better.

This would be great

[bsmth]

Leaving a +1 and we can follow-up with spec_urls or BCD 👍🏻

Should we add a TODO in 37811 so we don't forget?

[hamishwillee]

@bsmth Thanks. The TODO is effectively the BCD note in 37811 - I'm waiting on a slack response. If I don't get one then there will be no BCD and this won't change. So merging. If we do get one then I'll create a new PR with the tidy. The point you know I've given up on BCD is when I mark dev-docs-complete in the tracking issue.