Can't click through a feature in the features list

[jyasskin]

To Reproduce Steps to reproduce the behavior:

1. Go to https://chromestatus.com/features#For%20a%20text%20box%2C%20its%20edges
2. Notice the "CSS text-box-edge" result
3. Now click on that result
4. "Feature not found."

Additional context

Feature 5611463370866688 is present in https://chromestatus.com/features.json, but https://chromestatus.com/api/v0/features/5611463370866688 is a 404

[c6z3h]

TLDR: I think on the feature_v2.json it notes that this "maturity" is of Unknown status, unlike most other working ones which are Working draft. Might need them to complete and update the backend json data

looking at the Web Dev Tools / Network, seems this is the json for the offending result

{
        "blink_components": [
            "Blink>Layout>Inline"
        ],
        "breaking_change": false,
        "browsers": {
            "chrome": {
                "blink_components": [
                    "Blink>Layout>Inline"
                ],
                "bug": null,
                "devrel": [
                    "[email protected]"
                ],
                "flag": false,
                "intervention": false,
                "origintrial": false,
                "owners": [
                    "[email protected]",
                    "[email protected]"
                ],
                "prefixed": null,
                "status": {
                    "text": "No active development",
                    "val": 1
                }
            },
            "ff": {
                "view": {
                    "notes": null,
                    "text": "No signal",
                    "url": null,
                    "val": 5
                }
            },
            "other": {
                "view": {
                    "notes": null
                }
            },
            "safari": {
                "view": {
                    "notes": null,
                    "text": "No signal",
                    "url": null,
                    "val": 5
                }
            },
            "webdev": {
                "view": {
                    "notes": null,
                    "text": "No signals",
                    "url": null,
                    "val": 4
                }
            }
        },
        "created": {
            "by": "[email protected]",
            "when": "2024-01-25 05:08:44.058139"
        },
        "enterprise_impact": 1,
        "first_enterprise_notification_milestone": null,
        "id": 5611463370866688,
        "is_released": false,
        "milestone": null,
        "name": "CSS text-box-edge",
        "resources": {
            "docs": [],
            "samples": []
        },
        "standards": {
            "maturity": {
                "short_text": "Unknown status",
                "text": null,
                "val": 0
            },
            "spec": "https://drafts.csswg.org/css-inline-3/#text-edges"
        },
        "summary": "For a text box, its edges can be determined in many ways.\r\nThis feature allows developers to specify the metrics that they want the edges of the text box to be, and another CSS property of text-box-trim should trim the box accordingly.",
        "unlisted": false,
        "updated": {
            "by": "[email protected]",
            "when": "2024-01-25 06:07:04.310802"
        }
    },

whereas for another one that works, titled CSS text-box-trim and text-box-edge:

{
        "blink_components": [
            "Blink>Layout>Inline"
        ],
        "breaking_change": false,
        "browsers": {
            "chrome": {
                "blink_components": [
                    "Blink>Layout>Inline"
                ],
                "bug": "https://bugs.chromium.org/p/chromium/issues/detail?id=1411581",
                "devrel": [],
                "flag": false,
                "intervention": false,
                "origintrial": false,
                "owners": [
                    "[email protected]",
                    "[email protected]"
                ],
                "prefixed": null,
                "status": {
                    "text": "No active development",
                    "val": 1
                }
            },
            "ff": {
                "view": {
                    "notes": "",
                    "text": "No signal",
                    "url": null,
                    "val": 5
                }
            },
            "other": {
                "view": {
                    "notes": ""
                }
            },
            "safari": {
                "view": {
                    "notes": "",
                    "text": "No signal",
                    "url": null,
                    "val": 5
                }
            },
            "webdev": {
                "view": {
                    "notes": "",
                    "text": "No signals",
                    "url": null,
                    "val": 4
                }
            }
        },
        "created": {
            "by": "[email protected]",
            "when": "2023-02-14 06:14:59.871318"
        },
        "enterprise_impact": 1,
        "first_enterprise_notification_milestone": null,
        "id": 5174589850648576,
        "is_released": false,
        "milestone": null,
        "name": "CSS text-box-trim and text-box-edge",
        "resources": {
            "docs": [],
            "samples": []
        },
        "standards": {
            "maturity": {
                "short_text": "Working draft",
                "text": "Specification currently under development in a Working Group",
                "val": 4
            },
            "spec": "https://drafts.csswg.org/css-inline-3/#text-edges"
        },
        "summary": "This feature includes two CSS properties,  text-box-trim and text-box-edge.\ntext-box-trim specifies whether start/end/both sides should be trimmed or not, and text-box-edge specifies the how each edge should be trimmed.\nThese properties allow developers to have precise control over spacing, and ensure font metrics are respected during layout in terms of spacing.\n",
        "unlisted": false,
        "updated": {
            "by": "[email protected]",
            "when": "2024-01-30 04:08:28.581358"
        }
    },

[jrobbins]

I think what happened was that an old entry was marked deleted and a new entry was created. The new feature entry is https://chromestatus.com/feature/5611463370866688

So, there was a defect in that you saw a deleted entry on the old feature list. I have a feeling that that might have been stale data in a cache, or a logic error in the way that the features.json response was computed. We changed the UI implementation to use a different API call now and I can't repro the problem with it, so this seems fixed.