- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Tue, 24 Oct 2017 13:09:04 +0000
- To: public-secondscreen@w3.org
>if there's inconsistency between user agents it encourages web developers to hide the media element during remote playback to ensure a consistent experience Adding to that point: Web developers have been hiding the `<input type=file>` UI for ages and reimplemented it themselves for the same reason, see e.g. [the IE5-era technique][1], [a more modern technique][2], [another example][3]. IIRC restrictions to styling the said element were put in place for security reasons to mitigate attack where the user is tricked into opening the file chooser. Perhaps worth considering this viewpoint when we do decisions on this API. In particular, this seems to confirm web developers go the extra mile to create a consistent experience if needed. I feel they shouldn't be forced to without a good reason. [1]: https://www.quirksmode.org/dom/inputfile.html [2]: https://tympanus.net/codrops/2015/09/15/styling-customizing-file-inputs-smart-way/ [3]: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/file#Examples -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/remote-playback/issues/46#issuecomment-338984021 using your GitHub account
Received on Tuesday, 24 October 2017 13:09:08 UTC