4 ms·
Is it possible this was done for a reason? Users on the linked page report that it's not just keydown but also keypress and keyup. If the first two were disable
by porphyrogene 8y ago
Is it possible this was done for a reason? Users on the linked page report that it's not just keydown but also keypress and keyup. If the first two were disabled but keyup still worked that decision may have some (limited) justification because keyup is the only one that necessarily fires once per physical input by the user.
I don't want to give Apple more credit than they deserve but it is equally foolish to assume that everything that is not how I expect it to be is a mistake. Then again, maybe they just don't want people using iOS when they "should" be using OSX, which is the kind of judgemental decision-making for which Apple is known. From the linked bug report:
> Would be a huge benefit to the iPad community if arrow key events fired. That explains the lack of support by sites like Cloud9, plnkr, etc... I do a lot of web development in those IDEs to teach people and to brainstorm when I'm not at my computer so it would be awesome if the team got this in and it made its way to IOS.
- sigfubar 8y ago> it is equally foolish to assume that everything that is not how I expect it to be is a mistake This humble attitude saves me a lot of time on a daily basis.
- yjftsjthsd-h 8y agoIt also saves face; it is quite embarrassing to realize you've been complaining about something and suddenly discover that it works fine and you are wrong.
- om2 8y agoIn this case the humility is unnecessary, as the linked bug report includes Apple WebKit folks acknowledging that it's a bug and pointing to our internal bug tracking it (turns out it has to be fixed below the WebKit level).