If you truly didn't intend to misrepresent it, then you must have misunderstood it. That's difficult for me to imagine because it's quite straightforward, but p

If you truly didn't intend to misrepresent it, then you must have misunderstood it. That's difficult for me to imagine because it's quite straightforward, but perhaps you aren't a native speaker, or are undercaffeinated. He didn't say it was no less usable if "it isn't supported." He said, assuming it isn't supported, it is no less usable than not including the <hr> Put another way, HE is comparing usability on iOS of <select name="produce"> <option>Apple</option> <option>Pear</option> <hr> <option>Carrot</option> <option>Celery</option> </select> vs usability on iOS of <select name="produce"> <option>Apple</option> <option>Pear</option> <option>Carrot</option> <option>Celery</option> </select> whereas YOU are comparing usability on iOS of <select name="produce"> <option>Apple</option> <option>Pear</option> <hr> <option>Carrot</option> <option>Celery</option> </select> vs usability on other platforms of <select name="produce"> <option>Apple</option> <option>Pear</option> <hr> <option>Carrot</option> <option>Celery</option> </select> Those are different comparisons. Discussing iOS, he said "it’s no less usable with the <hr> than without." You made it seem like he said "it’s no less usable without support for <hr> than with support." That isn't what he said. Because <hr> in <select> is not supported on iOS, it is ignored. The resulting browser behavior is identical. It is impossible for one to be less usable than the other because the result is utterly down-to-the-pixel indistinguishable. As a result, eyelidlessness rightfully pointed out that lapcat was incorrect when he said "I can't share code between Mac and iOS." While the iOS experience would not be as good as the Mac experience, the iOS experience with the <hr> would be no less usable than the iOS experience would be without it.