MediaMIMEType factors out the main MIME "type/subtype" string from
MediaExtendedMIMEType, as it is often useful to deal with just that part.
Like MediaContentType and MediaExtendedMIMEType, MediaMIMEType is always valid
once constructed.
MozReview-Commit-ID: 5Urlk6OLo5q
--HG--
extra : rebase_source : aef60fde09b13befa1311c6cd712eac19c438021
This patch factors out all data handling of MIME strings from MediaContentType
to MediaExtendedMIMEType.
MediaExtendedMIMEType is pretty much a copy of the old MediaContentType, as the
functionality was fine (but will be modified in upcoming patches).
MediaContentType then just delegates the work to its embedded
MediaExtendedMIMEType field.
The main difference is that the default constructor and Populate() method have
been replaced with a single constructor that takes all the arguments at once.
MozReview-Commit-ID: GBAgPDT2DUW
--HG--
rename : dom/media/MediaContentType.cpp => dom/media/MediaMIMETypes.cpp
rename : dom/media/MediaContentType.h => dom/media/MediaMIMETypes.h
extra : rebase_source : 1c925d8e049d9d349ec4c3dd1a079f570b809970
This is required because the next patch adds new files, which changes the
unified-build order and exposes error due to this missing #include.
MozReview-Commit-ID: 3pmqNK1B2bR
--HG--
extra : rebase_source : 6e3dc2d4200aa4740b8f216ba1d1a131b94c26cb
On architectures like alpha and ia64, the glibc does not use the
canonical ABI version number 6 but 6.1 and therefore the filename
of the C library is not libc.so.6 but libc.so.6.1. We're therefore
making the Python code more flexible and use find_library from
ctypes.util to determine the filename from the environment instead
of hard-coding it.
--HG--
extra : rebase_source : 64676648cec9975045a6dfeae1cfc9213226e242
On architectures like alpha and ia64, the glibc does not use the
canonical ABI version number 6 but 6.1 and therefore the filename
of the C library is not libc.so.6 but libc.so.6.1. We're therefore
making the Python code more flexible and use find_library from
ctypes.util to determine the filename from the environment instead
of hard-coding it.
--HG--
extra : rebase_source : 66e1caf57f9743dc10698b93c7e1f1a1b3b67e85
This was accidentally overlooked in 1e0bcb0402b5 (bug 1231764).
MozReview-Commit-ID: IYxrRV9G5iW
--HG--
extra : rebase_source : 7ee0619fecc5b06e1dd6f1d2ef4ab23c21ce686c
System SVG rendering on Android 6.0 seems to be broken for certain VectorDrawable's:
these three icons were being distorted, only on Android 6. Using a different SVG
converter (an online converter, as opposed to the Android Studio converter),
results in the icons being rendered correctly.
MozReview-Commit-ID: 2INnb0clb54
--HG--
extra : rebase_source : 5b3fd9ca7354855c6ee70594b960f0098c98d974
The tests have to be skipped because Marionette server only allows the
installation of add-ons for Firefox. Once Fennec gets white-listed, it
would be still necessary to copy the to install XPI to the device file
system.
MozReview-Commit-ID: Jr53iCzkZvo
--HG--
extra : rebase_source : 2fef786cf8b114c2cbd002a6d2b37da51fcc8e5b
What you see first is the removal of the line `this._highlightAll = aHighlight;`, which is repeated in the `_setHighlightAll` method.
This line was put here initially to make the test_findbar_events.xul test pass but in fact makes it so that the pref is never set in `_setHighlightAll`!
In other words, we never actually persisted the 'Highlight All' state properly.
Reading further: the `_dispatchFindEvent` attaches some findbar state flags to the event details, including the value of `_highlightAll`.
Even though none of our consumers use it currently (haven't checked if TB does, though), you can cancel further execution of highlighting all ranges.
Since the `_setHighlightAll` doesn't do that kind of processing, but merely makes sure the internal state is up to snuff, is persisted properly and the buttons are updated, I moved it up to be invoked before dispatching the event.
MozReview-Commit-ID: 4BBy4FR1r5c
--HG--
extra : rebase_source : 204e77aaef3cd55886daeb2e0fdef84da1159c68
use properties-view
show other Cookie properties
MozReview-Commit-ID: 7526Hm2ORbL
--HG--
extra : rebase_source : 2e2850fd8daf6646648cc3e63c2a53cd381e90f3
Given that new windows are not supported in Fennec some of the screenshot tests for
chrome scope have to be skipped.
MozReview-Commit-ID: 5pE8xPdw1fS
--HG--
extra : rebase_source : b80c060a7fe355a243dabbbd7f9976d3be9afdcd
The test cannot be run on Fennec because there is no support for additionally
opened windows.
MozReview-Commit-ID: 7oDniZoYLN
--HG--
extra : rebase_source : 81dab6a260c3e805ed71342a93e12213f9a44952
