Firefox 153 implements new popover hint behavior

[hamishwillee]

FF153 implements the new popover hint specification in https://bugzilla.mozilla.org/show_bug.cgi?id=2029974

This version_removes the old implementation of the global hint attribute (that has the note about the old spec) and adds a new release version for the global attribute. This also updates HTMLElement.hint, which was omitted in the update in #29676 (probably by accident).

Note, this was not in the BCD collector run #29883

Related docs work can be tracked in mdn/content#44461

[github-actions]

Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs).

[caugner]

Should we consider the implementation of "an older version of the specification with inconsistent behavior" as a partial implementation?

Otherwise, there would be no need to split up the statement, as the note could say "Before Firefox 153, …"

[caugner]

Should we consider the implementation of "an older version of the specification with inconsistent behavior" as a partial implementation?

Forgot to cc @Elchi3 or @ddbeck.

[hamishwillee]

Should we consider the implementation of "an older version of the specification with inconsistent behavior" as a partial implementation?

@caugner There was already some discussion of that in #29676 (comment)

FWIW IMO no, on the basis that it wasn't a partial implementation: it was a full implementation of a buggy spec. I quite like the current approach. I'll leave for you lot to resolve how you want it though.

[caugner]

Should we consider the implementation of "an older version of the specification with inconsistent behavior" as a partial implementation?

@caugner There was already some discussion of that in #29676 (comment)

Thanks for the reminder. But doesn't Chrome 150 (stable) also implement the new version? If it was just Firefox 153 (beta), we might have wanted to wait, but now that both implementing engines implement the new version, we should be able to go ahead and mark the old version as partial (as suggested by Daniel in the linked comment). Technically, this reverts Firefox support from Stable to Beta, but I would think that's okay for 2 weeks until the 153 stable release.

[hamishwillee]

... But doesn't Chrome 150 (stable) also implement the new version? If it was just Firefox 153 (beta), we might have wanted to wait, but now that both implementing engines implement the new version, we should be able to go ahead and mark the old version as partial (as suggested by Daniel in the linked comment). Technically, this reverts Firefox support from Stable to Beta, but I would think that's okay for 2 weeks until the 153 stable release.

Yes it does https://developer.chrome.com/release-notes/150?hl=en#popoverhint_behavior_changes

Fixed as I think you wanted ("treat an older version of the specification with inconsistent behavior as a partial implementation")

FWIW I would have said "that is inconsistent with how BCD works". Seems like there is support for the idea in that thread though, and I don't feel strongly.