We believe the rate is constrained by the audio driver in practice,
but want to verify this assumption. The valid range 8-192 kHz covers
all sample rates in general use for audio data.
Note we must use an error return instead of an assertion since these
bounds are verified by unit tests, which do not catch MOZ_ASSERT().
Also, in order to prevent the MediaDecoderStateMachine to stall waiting for audio data,
feed back as many decoded audio frame as were first submitted to the decoder in one go.
This makes APZ behave nicely with most uses of a css transform:scale.
Summary of changes:
- FrameMetrics::mCumulativeResolution now includes the css-driven resolution
in addition to the pres-shell resolution.
- Displayports are now stored in Screen pixels rather than Layer pixels.
This is what we want anyways (as we'd like the displayport size to remain
constant as a fraction of the screen size), but it was necessary to make
this change as part of this patch because continuing to store them in
Layer pixels in the presence of a css-driven resolution would have
required a bunch of infrastructure to implement correctly.
Remaining work:
- Layout painting a scrollable layer at a resolution different from the
scale induced by the css transform causes problems. These will go away
with bug 1076192.
- Different resolutions on the x and y axes are not supported. This is
tracked by bug 1039967.
Reopens the MediaSource when SourceBuffer::Remove is called on an Ended
MediaSource.
Only run the Range Removal algorithm when MediaSource duration is changed
instead of calling Remove on SourceBuffers.
Updates tests for the fact that update{start,end} can now be called
more than once due to DurationChange.
--HG--
extra : rebase_source : efe01de2f7c6be09b29e2e19d69d9943c9ab5e52
The interesting feature JSONWriteFunc has, contrary to JSONWriter, is that it
only has virtual methods, which makes it a better candidate to be passed
around between libraries not linked against each other.
This will allow to make dmd and libxul independent from each other.
========
https://hg.mozilla.org/integration/gaia-central/rev/ebb431673edc
Author: David Flanagan <dflanagan@mozilla.com>
Desc: Merge pull request #26047 from davidflanagan/bug1079692
Bug 1079692: update video thumbnail title asynchonously so we don't block when user rotates phone r=johnhu
========
https://hg.mozilla.org/integration/gaia-central/rev/56c7781bce82
Author: David Flanagan <dflanagan@mozilla.com>
Desc: Bug 1079692: update video thumbnail title asynchonously so we don't block when the user rotates the phone
fix spelling error in method name
update test busted by spelling correction
========
https://hg.mozilla.org/integration/gaia-central/rev/643dbb1c26d3
Author: Chris Lord <chrislord.net@gmail.com>
Desc: Merge pull request #26006 from Cwiiis/bug1082675-app-grouping-by-default
Bug 1082675 - Enable homescreen app-grouping permanently. r=kgrandon,crdlc
========
https://hg.mozilla.org/integration/gaia-central/rev/01889de35710
Author: Chris Lord <chrislord.net@gmail.com>
Desc: Bug 1082675 - Fix divider->group related marionette test failures. r=crdlc,kgrandon
Some assumptions made by marionette tests no longer hold after enabling
app-grouping by default:
- Long-pressing a divider no longer brings up the context menu
- The divider element itself is not positioned (its children are)
========
https://hg.mozilla.org/integration/gaia-central/rev/89e940eb62b0
Author: Chris Lord <chrislord.net@gmail.com>
Desc: Bug 1082675 - Enable homescreen app-grouping permanently. r=kgrandon,crdlc
This reverts commit 071efd0eb9d962d4f96edc28d672e48910f48387.