html.elements.hr - iOS Safari 17.x supports the feature, Android Chrome doesn't about browser-compat-data

[aardrian]

@dfabulich

• Chrome 123 / Android 13: does not expose the <hr> visually in the page (contradicting @aardrian's findings)

That does not contradict my findings. It's a different result using a different browser release. As I note in the post, I tested Chrome Canary (120) / Android 13. That is a different release than what you tested.

• Safari 17.4 / iPadOS 17.4: exposes the <hr> visually in the page (contradicting @aardrian's findings)

That does not contradict my findings. It's a different result using a different browser release. As I note in the post, I tested Safari on iPadOS 17.0.3. That is a different release than what you tested.

The Safari team announced that <hr> in <select> had come to Safari 17. In #21648, @aardrian tested this in "Safari 17" (presumably Safari 17.0) and find that it worked on macOS 14.0, but not on iPadOS 17.0.3. That really doesn't make sense to me; it makes me wonder whether @aardrian was somehow accidentally testing the wrong version of Safari/iPadOS…?

It doesn't make sense to you because you are assuming the Safari release is not tied to the iDeviceOS release. Technically I tested Safari 17.0.3 and you tested Safari 17.4.

I have since upgraded my iDevice, so I cannot provide a screen shot. I have not updated Chrome Canary on my Android, so I can provide a screen shot, which follows.

Observe how it exposes the <hr> as its own empty selectable option. You asserted I claimed it "does not expose the <hr> visually in the page", though the prior sentence is what I wrote in the post (because I copied it from there).

Anyway, this issue is really about more recent support than my testing. It should be filed as that since there is no evidence that what I reported for the versions I tested was wrong. If you have evidence (by testing the specific versions I tested), then please add it. Otherwise consider renaming and re-scoping this issue (especially since Safari 17.x supporting it is not accurate).

[dfabulich]

I'm going to close and re-file this issue as two issues, to distinguish the two topics.

[dfabulich]

Split off #22729 and #22730.