@ Prst. V.Jeltz
So the programmer is now responsible for ...
... for pointing out when a request appears to make no sense.
When some PHB asks you for a print button in a webpage, do you
(a) add a "print" button because you know no better
(b) add a button labelled "print", and surreptitiously check PHB's browser settings for what will work for him?
(c) point out that print is a browser function, and that to do it from a web page is at best re-inventing a wheel, and at worst a security hole (when someone compromises their own security so it'll "work" for them).
OK, the webpage is one scenario among many. In another case, the arguments might be different, and a sensible outcome might include the button. But I suspect that's not the kind of scenario where your programmer is pushing back against a request.