update release, add doc note about krom being crippleware as usual

teodesian · Nov 8, 2019 · 1171e00 · 1171e00
1 parent ae84636
commit 1171e00
Show file tree

Hide file tree

Showing 3 changed files with 9 additions and 1 deletion.
diff --git a/Changes b/Changes
@@ -1,5 +1,11 @@
 Revision history for Selenium-Remote-Driver
 
+1.36  10-21-2019 TEODESIAN
+        [BUG FIXES]
+        - Adjust handling of chrome due to it implementing WC3 mostly correctly now
+        - Fix browser detection logic in screenshot()
+        - Actually apply the fix from 1.35 in the right place, heh
+
 1.35  10-21-2019 TEODESIAN
         [BUG FIXES]
         - Fix race condition and inability to find a port in certain circumstances when using direct driver modules.

diff --git a/dist.ini b/dist.ini
@@ -1,5 +1,5 @@
 name = Selenium-Remote-Driver
-version = 1.35
+version = 1.36
 author = George S. Baugh <george@troglodyne.net>
 author = Aditya Ivaturi <ivaturi@gmail.com>
 author = Daniel Gempesaw <gempesaw@gmail.com>

diff --git a/lib/Selenium/Remote/Driver.pm b/lib/Selenium/Remote/Driver.pm
@@ -248,6 +248,8 @@ WD3 enabled server with chromedriver enabled.
 
     https://sites.google.com/a/chromium.org/chromedriver/capabilities
 
+Also, if you instantiate the object in WC3 mode (which is the default), the remote driver will throw exceptions you have no choice but to catch,
+rather than falling back to JSONWire methods where applicable like geckodriver does.
 
 =head1 CONSTRUCTOR