Blink and webkit launch focusin after focus and focusout after blur. Despite
this contradiction with the spec, it is best to mirror this new way, as there
is little guidance or existing code to clarify implementation amiguities that
can arise from the spec.
If focus/blur is fired on a window or document, or the event triggers a change
of focus, do not fire the corresponding focusin/focusout. Otherwise, always
fire the corresponding event.
Additionally, add a mochitest and a w3c-platform-test.
MozReview-Commit-ID: AgQ8JBxKIqK
This commit does the following.
- Converts the test to a gtest, including renaming the directory.
- Factors out the duplicated checking code into a separate Check() function.
- Avoids printing any output unless a failure occurs. (The gtest harness prints
out minimal output, like the name of the current test.)
- Removes SampleWordBreakUsage(), which prints some output but doesn't actually
test anything, and so isn't useful.
--HG--
rename : intl/lwbrk/tests/TestLineBreak.cpp => intl/lwbrk/gtest/TestLineBreak.cpp
rename : intl/lwbrk/tests/moz.build => intl/lwbrk/gtest/moz.build
extra : rebase_source : e673299e237a1a8a3b0a33cfc0a0024ab7dee271
This required moving template function ValidateEvent into the .h file to avoid
linking problems in xul-gtest.
--HG--
rename : dom/media/webaudio/compiledtest/TestAudioEventTimeline.cpp => dom/media/webaudio/gtest/TestAudioEventTimeline.cpp
rename : dom/media/webaudio/compiledtest/moz.build => dom/media/webaudio/gtest/moz.build
extra : rebase_source : 1a8917fc0e75e9c264bc88aec5565d9fff085c12
When dumping buffered messages in mochitest, this adds a new log line for every second's
worth of messages. Alternatively we could print the timestamp in brackets at the end of
each buffered message, but I found that in practice there tends to be many log messages
generated each second. This looks better for that case, but will look much worse if logs
are generated more than a second apart. I would be ok with either method.
MozReview-Commit-ID: Jkd9hOlmiGZ
--HG--
extra : rebase_source : 6c7a10235c2c7ca4a483ea7f1f37e18690974ce0
I believe the current behaviour of buffering messages outside of a test is wrong. For example:
1. INFO logged -> gets buffered
2. TEST-START logged -> doesn't get buffered
3. Test fails and buffer dumped -> INFO looks like it happened after the TEST-START
I think this is very confusing as developers trying to debug a test will think that INFO message
is happening somewhere inside their test when in reality it isn't.
MozReview-Commit-ID: Jkd9hOlmiGZ
--HG--
extra : rebase_source : f016cb069abcb71587a1d9df143e4796ffa69b3b
For some reason we have a 'buffering' parameter in the MessageLogger constructor, but
then rather than using this, the mochitest harness modifies state after instantiation.
Using the constructor is easier to understand, and simplifies some of the logic in the
next couple of patches.
MozReview-Commit-ID: Jkd9hOlmiGZ
--HG--
extra : rebase_source : eb2b5b7d647d69229cca5495f6f950c5fcf80809
This changeset adds a taskcluster specific mozharness script and posix config
for the external media tests. It also removes some of the no longer needed
config from the windows task cluster config for these tests.
MozReview-Commit-ID: 1E5fkFV5DeV
--HG--
extra : rebase_source : 268b09da0601b32e61a24195f703de0578de1317
This causes consumers managing defaults themselves to fail to find a default
subsuite for tests, because the manifestparser will have provided a blank
default value by the time they incorporate defaults into a test definition.
This patch removes the provided defaults and updates a number of places assuming
the 'subsuite' field is always present.
MozReview-Commit-ID: 1jPy52VmEPr
The spec used to say that getting the .ping property on
HTMLAnchorElement or HTMLAreaElement should return a DOMTokenList of
parsed URLs, but it now says to return a plain string. All other UAs
that implement ping match the new spec, and it's hopefully unlikely that
any sites depend on our old behavior.
Discussion: https://github.com/whatwg/html/issues/1780
MozReview-Commit-ID: LpmH8ANNT9g
We now pass almost all the upstream EME WPT, but out local copy is out
of date, so we're failing some. So rather than mark them as expected fail,
update the out copy so that the tests pass as expected.
MozReview-Commit-ID: 7YnD6Dlc0HC
--HG--
extra : source : 7862f7d272567d284cea8665d12258c758c9f439
This allows other UAs to use it, removes duplicated checks, and
increases the chance of us noticing if the spec changes. Some of the
expected values in our mochitest were contrary to the spec.
I checked the new expected failures against the spec and the other UAs.
I filed a spec bug for one group because it was contrary to all UAs
(although IMO the spec makes more sense and the UAs are buggy), and the
others are fixed in the next patch.
MozReview-Commit-ID: 1j11XgfuErB
This causes consumers managing defaults themselves to fail to find a default
subsuite for tests, because the manifestparser will have provided a blank
default value by the time they incorporate defaults into a test definition.
This patch removes the provided defaults and updates a number of places assuming
the 'subsuite' field is always present.
MozReview-Commit-ID: 1jPy52VmEPr
--HG--
extra : rebase_source : be7a2504af6853abb1bc532a058738f33d8dcbee
I haven't seen a case of this happening in the wild, but I believe it is possible for a test to dump "TEST-UNEXPECTED-FAIL"
directly to the log and mozharness using the StructuredOutputParser would not pick it up. This patch is just me being extra
careful to flag potential errors like that. I'm not sure they even exist.
This patch also purposefully uses substr to avoid requiring said string to show up at the beginning, which should avoid
certain prefix issues we've run into in the past.
MozReview-Commit-ID: 99n9YizlEDH
--HG--
extra : rebase_source : 2063f2fc4ca109a4ac24ccdbc0672e4e1b4c0fb6
We were previously logging these at the info level as a really hacky way to make sure that the mozharness
output parser was able to detect them. Since bug 1261194 switched mochitests to use the StructuredOutputParser,
we now need to log them at the error level or they won't get picked up anymore.
MozReview-Commit-ID: 99n9YizlEDH
--HG--
extra : rebase_source : a3495ac3c3d770f1eabadca42fd4c2f789e83617
Phil Ringnalda
Henrik Skupin
Kevin Wern
Wes Kocher
Sebastian Hengst
Kim Moir
Bevis Tseng
Gabor Krizsanits
Nicholas Nethercote
Nebelhom
Andrew Halberstadt
Joel Maher
Carsten "Tomcat" Book
Rob Thijssen
Jean-Yves Avenard
Boris Chiou
Bryce Van Dyk
Michelangelo De Simone
Kris Maglione
Chris Manchester
Jordan Lund
Aryeh Gregor
Ryan VanderMeulen
Mark Banner
Chris Peterson
Eugen Sawin
Randell Jesup
Chris Pearce
Michael Layzell
Geoff Brown
Masatoshi Kimura
Maja Frydrychowicz
Cody Tran
ctai
Shih-Chiang Chien
James Cheng
Andreas Farre
Paul Yang
Bob Clary