Manually set the support status of advanced attr()

There is no BCD entry for attr() working outside of the content
property for pseudo-elements, so this is the only way right now.

Author: foolip

features/attr.yml

@@ -3,6 +3,15 @@ description: "The `attr()` CSS function, in the context of any property, returns
 spec: https://drafts.csswg.org/css-values-5/#attr-notation
 caniuse: css3-attr
 group: css
+# There is no BCD entry for attr() support beyond the `contents` property
+# (a.k.a. advanced attr()) so the status here is maintained manually, matching
+# https://caniuse.com/css3-attr and https://chromestatus.com/feature/4680129030651904.
+status:
+  baseline: false
+  support:
+    chrome: "133"
+    chrome_android: "133"
+    edge: "133"
 compat_features:
   # The css.types.attr key makes sense here but is already used in `contents-attr`
   #- css.types.attr

features/attr.yml.dist

@@ -1,9 +1,6 @@
 # Generated from: attr.yml
 # Do not edit this file by hand. Edit the source file instead!
 
-status:
-  baseline: false
-  support: {}
 compat_features:
   # baseline: low
   # baseline_low_date: 2025-03-31
@@ -17,14 +14,14 @@ compat_features:
   #   safari_ios: "18.4"
   - css.types.attr.fallback
 
+  # ⬇️ Same status as overall feature ⬇️
   # baseline: false
   # support:
   #   chrome: "133"
   #   chrome_android: "133"
   #   edge: "133"
   - css.types.attr.type-or-unit
 
-  # ⬇️ Same status as overall feature ⬇️
   # baseline: false
   # support: {}
   - css.types.attr.type-or-unit.angle