Kaynağa Gözat

Fix #443 - document nonstandard behavior of driver vendors in generalAction

George S. Baugh 5 yıl önce
ebeveyn
işleme
009b491a76
2 değiştirilmiş dosya ile 12 ekleme ve 1 silme
  1. 2 1
      dist.ini
  2. 10 0
      lib/Selenium/Remote/Driver.pm

+ 2 - 1
dist.ini

@@ -1,5 +1,5 @@
 name = Selenium-Remote-Driver
-version = 1.38
+version = 1.39
 author = George S. Baugh <george@troglodyne.net>
 author = Aditya Ivaturi <ivaturi@gmail.com>
 author = Daniel Gempesaw <gempesaw@gmail.com>
@@ -86,3 +86,4 @@ encoding = bytes
 ; authordep XML::Simple = 0
 ; authordep Test::LWP::UserAgent = 0
 ; authordep Test::Pod::Coverage = 0
+; authordep Term::UI = 0

+ 10 - 0
lib/Selenium/Remote/Driver.pm

@@ -1402,6 +1402,16 @@ Called with no arguments, it simply executes the existing action queue.
 If you are looking for pre-baked action chains that aren't currently part of L<Selenium::Remote::Driver>,
 consider L<Selenium::ActionChains>, which is shipped with this distribution instead.
 
+=head3 COMPATIBILITY
+
+Like most places, the WC3 standard is openly ignored by the driver binaries.
+Generally an "actions" object will only accept:
+
+    { type => ..., value => ... }
+
+When using the direct drivers (E.G. Selenium::Chrome, Selenium::Firefox).
+This is not documented anywhere but here, as far as I can tell.
+
 =cut
 
 sub general_action {