Add standardizing-security-semantics-of-cross-site-cookies

[browser-specs-bot]

URL

https://w3c.github.io/webappsec-standardizing-security-semantics-of-cross-site-cookies/

Rationale

• See repository: w3c/webappsec-standardizing-security-semantics-of-cross-site-cookies
• Would-be shortname: standardizing-security-semantics-of-cross-site-cookies

Additional properties

{}

[browser-specs-bot]

Changes to index.json

This update would trigger the following changes in index.json:

Add spec (1)

{
  "url": "https://w3c.github.io/webappsec-standardizing-security-semantics-of-cross-site-cookies/",
  "seriesComposition": "full",
  "shortname": "standardizing-security-semantics-of-cross-site-cookies",
  "series": {
    "shortname": "standardizing-security-semantics-of-cross-site-cookies",
    "currentSpecification": "standardizing-security-semantics-of-cross-site-cookies",
    "title": "Standardizing Security Semantics of Cross-Site Cookies",
    "shortTitle": "Standardizing Security Semantics of Cross-Site Cookies",
    "nightlyUrl": "https://w3c.github.io/webappsec-standardizing-security-semantics-of-cross-site-cookies/"
  },
  "organization": "W3C",
  "groups": [
    {
      "name": "Web Application Security Working Group",
      "url": "https://www.w3.org/groups/wg/webappsec/"
    }
  ],
  "nightly": {
    "url": "https://w3c.github.io/webappsec-standardizing-security-semantics-of-cross-site-cookies/",
    "status": "Editor's Draft",
    "alternateUrls": [],
    "repository": "https://github.com/w3c/webappsec-standardizing-security-semantics-of-cross-site-cookies",
    "sourcePath": "index.bs",
    "filename": "index.html"
  },
  "title": "Standardizing Security Semantics of Cross-Site Cookies",
  "source": "spec",
  "shortTitle": "Standardizing Security Semantics of Cross-Site Cookies",
  "categories": [
    "browser"
  ],
  "standing": "good"
}

Tests

These changes look good! 😎

[tidoust]

Shortname is 54 characters long and would become the longest shortname in the list. Sorting shortnames from longest to shortest, I note that the longest ones are those that extend a base spec somehow, see list below. Should we recommend adopting a, ahem, shorter shortname for that base spec before we add it to the list?

54 standardizing-security-semantics-of-cross-site-cookies
52 WEBGL_multi_draw_instanced_base_vertex_base_instance
46 WEBGL_draw_instanced_base_vertex_base_instance
42 wasm-js-api-2-fork-content-security-policy
41 wasm-js-api-2-fork-js-promise-integration
39 tc39-async-explicit-resource-management
39 webcodecs-video-frame-metadata-registry
38 WEBGL_blend_equation_advanced_coherent
38 user-preference-media-features-headers <- only base spec with a >30 character long shortname, not yet published to /TR/
37 wasm-js-api-2-fork-exception-handling
37 wasm-js-api-2-fork-js-string-builtins
36 wasm-core-2-fork-function-references
35 webcodecs-vorbis-codec-registration
34 WEBGL_compressed_texture_s3tc_srgb
34 wasm-js-api-2-fork-esm-integration
33 tc39-explicit-resource-management
33 mse-byte-stream-format-mpeg-audio
33 webcodecs-alaw-codec-registration
33 webcodecs-flac-codec-registration
33 webcodecs-hevc-codec-registration
33 webcodecs-opus-codec-registration
33 webcodecs-ulaw-codec-registration
32 webcodecs-aac-codec-registration
32 webcodecs-av1-codec-registration
32 webcodecs-avc-codec-registration
32 webcodecs-mp3-codec-registration
32 webcodecs-pcm-codec-registration
32 webcodecs-vp8-codec-registration
32 webcodecs-vp9-codec-registration
31 EXT_disjoint_timer_query_webgl2
31 wasm-core-2-fork-branch-hinting
31 wasm-core-2-fork-extended-const
31 mse-byte-stream-format-registry
30 EXT_texture_filter_anisotropic
30 WEBGL_compressed_texture_pvrtc
30 tc39-dynamic-code-brand-checks
30 mse-byte-stream-format-isobmff

[dontcallmedom]

+1 - "standardizing" is not needed for sure; possible alternatives (shortest/preferred to longest/least disruptive):

• secure-x-site-cookies
• security-semantics-x-site-cookies
• security-semantics-cross-site-cookies