Range#cloneContents starts playing audio
Reported by
woxxom@gmail.com,
May 26 2018
|
|||||
Issue descriptionChrome: all versions ====================================== 1. open the attached test.html 2. if it doesn't play automatically, click the play button Expected: one popping sound Observed: two popping sounds ====================================== In the attached code Range#cloneContents was meant to get a copy of DOM for further processing, but due to the observed behavior it's effectively unusable. It may be an issue with the DOM spec, https://dom.spec.whatwg.org/#dom-range-clonecontents
,
May 28 2018
Able to reproduce the issue using #68.0.3440.6 and 66.0.3359.181 on Win 10, Linux Debian Rodete and Mac 10.13.3 as per the step mentioned in original comment. Heard two popping sounds This seems to be a Non-Regression as same behavior is observed across all the channels since M60. Untriaging for further inputs. Thanks!!
,
May 30 2018
Add the Media component. According to https://dom.spec.whatwg.org/#concept-range-clone the cloned range is a fragment, so not attached to the document. I seems like media that is not attached to a document should not play.
,
Jul 3
,
Jul 4
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by susan.boorgula@chromium.org
, May 27 2018