:cpearce it feels like your argument for why space is supported, but tab isn't, undermines itself: if space is supported because it's commonly used in desktop media players, then there should be no objection to supporting tab as well, as that's commonly used to activate the document in desktop browsers: 1. put https://pearce.org.nz/video/autoplay.html in chrome's URL bar and hit enter, 2. wait a few seconds, 3. tab into the document, 4. the video start playing. Given that Chrome effectively defines what is "common" these days (as much as I wish that weren't true), that feels reason enough to add support for tab as well, as that's what people will be used to now. (I'd mention what Edge does, but given that that's about to become Chrome, its behaviour is going to be "whatever Chrome already does", so that just adds to the argument that tab is commonly used to activate the document).
Bug 1530220 Comment 17 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
@cpearce it feels like your argument for why space is supported, but tab isn't, undermines itself: if space is supported because it's commonly used in desktop media players, then there should be no objection to supporting tab as well, as that's commonly used to activate the document in desktop browsers: 1. put https://pearce.org.nz/video/autoplay.html in chrome's URL bar and hit enter, 2. wait a few seconds, 3. tab into the document, 4. the video start playing. Given that Chrome effectively defines what is "common" these days (as much as I wish that weren't true), that feels reason enough to add support for tab as well, as that's what people will be used to now. (I'd mention what Edge does, but given that that's about to become Chrome, its behaviour is going to be "whatever Chrome already does", so that just adds to the argument that tab is commonly used to activate the document).
@cpearce it feels like your argument for why space is supported, but tab isn't, undermines itself: if space is supported because it's commonly used in desktop media players, then there should be no objection to supporting tab as well, as that's commonly used to activate the document in desktop browsers: 1. put https://pearce.org.nz/video/autoplay.html in chrome's URL bar and hit enter, 2. wait a few seconds, 3. tab into the document, 4. the video starts playing. Given that Chrome effectively defines what is "common" these days (as much as I wish that weren't true), that feels reason enough to add support for tab as well, as that's what people will be used to now. (I'd mention what Edge does, but given that that's about to become Chrome, its behaviour is going to be "whatever Chrome already does", so that just adds to the argument that tab is commonly used to activate the document).
@cpearce it feels like your argument for why space is supported, but tab isn't, undermines itself: if space is supported because it's commonly used in desktop media players, then there should be no objection to supporting tab as well, as that's commonly used to activate the document in desktop browsers: 1. put https://pearce.org.nz/video/autoplay.html in chrome's URL bar and hit enter, 2. wait a few seconds, 3. tab into the document, 4. the video starts playing. Given that Chrome effectively defines what is "common" these days (as much as I wish that weren't true), that feels reason enough to add support for tab as well, as that's what people will be used to now. (I'd mention what Edge does, but given that that's about to become Chrome, its behaviour is going to be "whatever Chrome already does", so that just adds to the argument that tab is commonly used to activate the document).
@cpearce it feels like your argument for why space is supported, but tab isn't, undermines itself: if space is supported because it's commonly used in desktop media players, then there should be no objection to supporting tab as well, as that's commonly used to activate the document in desktop browsers: 1. put https://pearce.org.nz/video/autoplay.html in chrome's URL bar and hit enter, 2. wait a few seconds, 3. tab into the document, 4. the video starts playing. Given that Chrome effectively defines what is "common" these days (as much as I wish that weren't true), that feels reason enough to add support for tab as well, as that's what people will be used to by now. (I'd mention what Edge does, but given that that's about to become Chrome, its behaviour is going to be "whatever Chrome already does", so that just adds to the argument that tab is commonly used to activate the document).