4 ms·
The use of serving <hr>-in-<select> to iOS is to avoid having to maintain two different code bases, which is an anticipated problem you specifically complained
by torstenvl 3y ago
The use of serving <hr>-in-<select> to iOS is to avoid having to maintain two different code bases, which is an anticipated problem you specifically complained about, saying "I can't share code between Mac and iOS."
Choosing to serve different code to different browsers complicates development and maintenance, for almost no upside (minuscule bandwidth savings).
Serving the same code, including serving <hr>-in-<select> to iOS, has the significant benefit of simplifying development and maintenance, has the benefit of automatically "upgrading" iOS users to your better experience once their browser supports it, and has no negative impact on usability (the iOS <select> looks and behaves identically with or without the <hr>).
That is the point eyelidlessness is trying to make. There are two courses of action, one of which has a lot of downside and little upside, the other has a fair amount of upside and no downside. That's what he meant when he pointed out that "it’s no less usable with the <hr> than without."
- lapcat 3y ago> Choosing to serve different code to different browsers complicates development and maintenance, I didn't say I was going to serve different code to different browsers. I said I would have to serve different code to different browsers if I used <hr> in <select>. That's a hypothetical. The alternative is actually to use a totally different technique for separating options that works on both desktop and mobile. > for almost no upside (minuscule bandwidth savings). It's not about bandwith! It's 100% about the user interface. That's what neither you nor eyelidlessness seems to understand. The entire point of using <hr> in <select>, or some other technique for separating options, is for the user interface. > no negative impact on usability (the iOS <select> looks and behaves identically with or without the <hr>). What you describe is a usability problem. That's a bug, not a feature. It really boggles my mind that you can't understand the basic requirement: I want to separate the options on both Mac and iOS. Leaving the options unseparated on iOS is not an acceptable alternative.
- torstenvl 3y ago[flagged]
- cxr 3y agoIt sounds like when you say "requirement" and that you "can't share code" and the result would be "unacceptable", you mean something else. Something like, "I just don't want it like this (even though there's not actually any hard and practical requirement here that it does the thing I want)".
- lapcat 3y ago> even though there's not actually any hard and practical requirement here that it does the thing I want The practical requirement is the user interface. The entire purpose of the <hr> in <select> is to visually separate the options for the user. If the visual separator only appears for some users but not for other users, that's a failure of the user interface. Imagine if it wasn't Mac vs. iOS users but rather that there was a WebKit bug where the <hr> only appeared 50% of the time, randomly, for Mac users. Wouldn't you consider that to be a problem?
- cxr 3y agoYes—a bug, even. Still doesn't change the meaning of "requirement".