1) Lines 172-174 deal with the Selenium error regarding an intercepted click. It seems as though the original implementation would instead click on the asynchronous process operating the drop-down recent search menu. Use of the execute_script() function seems to circumvent that.
2) Lines 214-215 in this new commit use .split() so that job and location represent words found in job_titles and locations delimited by spaces. The original implementation saw only the first letter of job and location being used in LinkedIn's search boxes. However, this does present an issue when cities with multi-word names are targeted ("Los Angeles", "New York").
Hope that's at least a bit helpful since all of this was personally new for me, really cool program man!
1) Lines 172-174 deal with the Selenium error regarding an intercepted click. It seems as though the original implementation would instead click on the asynchronous process operating the drop-down recent search menu. Use of the execute_script() function seems to circumvent that. 2) Lines 214-215 in this new commit use .split() so that job and location represent words found in job_titles and locations delimited by spaces. The original implementation saw only the first letter of job and location being used in LinkedIn's search boxes. However, this does present an issue when cities with multi-word names are targeted ("Los Angeles", "New York").
Hope that's at least a bit helpful since all of this was personally new for me, really cool program man!