Commit Graph

12 Commits

Author SHA1 Message Date
John Firebaugh
01332ebead Omit "should" in spec descriptions
The rationale is this: the spec string describes the expected
behavior unconditionally. The code examples, on the other hand,
set up an expectation that is tested with the call to the expect
method. The code examples can violate the expectation, but the
spec string does not. The value of the spec string is as clearly
as possible describing the behavior. Including “should” in that
description adds no value. (From http://rubyspec.org/style_guide/)
2013-02-19 12:41:48 -08:00
Vladimir Agafonkin
8e176f48aa Merge pull request #1419 from tmcw/test-jshint
Fix semicolons, breaking, whitespace, duplicate var statements.
2013-02-19 08:25:51 -08:00
Vladimir Agafonkin
aea0e3b05b fix browser test runner, close #1418 2013-02-19 18:21:01 +02:00
Tom MacWright
0a2000166a Fix semicolons, breaking, whitespace, duplicate var statements. 2013-02-19 11:18:15 -05:00
Vladimir Agafonkin
c327fa89ee add a couple of DomUtil tests, #1347 2013-02-05 17:01:01 +02:00
Pascal Borreli
9546599520 Fixed typos 2012-11-09 23:15:48 +00:00
Andrey Rublev
b27922ea2c Add L.DomUtil.removeClass method 2011-07-15 19:03:35 +07:00
mourner
ad46474275 added getStyle, fixed setPosition 2010-09-14 14:57:45 +03:00
mourner
391e57c144 placeholder for spec 2010-09-13 19:02:49 +03:00
mourner
6a158218c1 DomUtil.get, spec 2010-09-07 17:02:45 +03:00
mourner
88ef7d1667 DomEvent fixes, specs 2010-09-07 15:04:00 +03:00
mourner
42bcb9b3b3 DomUtil, DomEvent, namespace config improvements, some specs 2010-09-07 14:27:44 +03:00