Appium 1.3.1 and above broken for click on WEBVIEW element

this blocks me from writing new webview test for iOS 8 now
css selector lookup is broken on 1.3.1 please go through the gist.
Broken from line 286 which manifest into a element not found issue on line 418 https://gist.github.com/braghome/851ef328cc41177793ff
the same test runs fine on 1.2.0

just trying to set my expectations here :wave: any reason why this feature was removed? @jonahss @jlipps @isaac @bootstraponline
The thing is on a Render.js based web app the only way to predictable with automation is to poll for web elements as the time in which dom elements show is unpredictable at best i.e.
two example of a good passing test on sauce

POST element
1m 13s (+0.02s)
using: "css selector"
value: "button[data-action='signinForm']"
=> {"ELEMENT":"5008"}
GET element/5008/displayed
1m 13s (+0.02s)
=> true
GET element/5008/enabled
1m 13s (+0.02s)
=> true
POST element/5008/click
1m 13s (+0.10s)
id: "5008"
=> null
POST element
1m 14s (+0.06s)
using: "css selector"
value: "a[data-tracking='account']"
=> {"ELEMENT":"5009"}
GET element/5009/displayed
1m 14s (+0.08s)
=> true
GET element/5009/text
1m 14s (+0.04s)
=> "Beakthis"
DELETE /session/1b1cc861e7f1406495237a69c08b6fd9
1m 14s (+1h 0s)
=> ""

different run of the same passing test

POST element
1m 32s (+0.01s)
using: "css selector"
value: "button[data-action='signinForm']"
=> {"ELEMENT":"5008"}
GET element/5008/displayed
1m 32s (+0.01s)
=> true
GET element/5008/enabled
1m 32s (+0.01s)
=> true
POST element/5008/click
1m 32s (+0.03s)
id: "5008"
=> null
POST element
1m 32s (+0.01s)
using: "css selector"
value: "a[data-tracking='account']"
=> An element could not be located on the page using the given search parameters.
POST element
1m 32s (+0.01s)
using: "css selector"
value: "a[data-tracking='account']"
=> An element could not be located on the page using the given search parameters.
POST element
1m 32s (+0.01s)
using: "css selector"
value: "a[data-tracking='account']"
=> An element could not be located on the page using the given search parameters.
POST element
1m 32s (+0.01s)
using: "css selector"
value: "a[data-tracking='account']"
=> An element could not be located on the page using the given search parameters.
POST element
1m 33s (+0.01s)
using: "css selector"
value: "a[data-tracking='account']"
=> An element could not be located on the page using the given search parameters.
POST element
1m 33s (+0.01s)
using: "css selector"
value: "a[data-tracking='account']"
=> An element could not be located on the page using the given search parameters.
POST element
1m 33s (+0.01s)
using: "css selector"
value: "a[data-tracking='account']"
=> An element could not be located on the page using the given search parameters.
POST element
1m 33s (+0.01s)
using: "css selector"
value: "a[data-tracking='account']"
=> An element could not be located on the page using the given search parameters.
POST element
1m 33s (+0.01s)
using: "css selector"
value: "a[data-tracking='account']"
=> {"ELEMENT":"5009"}
GET element/5009/displayed
1m 33s (+0.02s)
=> true
GET element/5009/text
1m 33s (+0.02s)
=> "Beakthis"
DELETE /session/3b4b647a493346b5a90119c4f13af054
1m 33s (+1h 7m 0s)
=> ""

Find by css selector in a webview should work. If it’s broken then the bug should be reported on GitHub so the developers fix it.

done https://github.com/appium/appium/issues/4340, sorry I assumed incorrectly that posting on this forum would automatically open the bug

@bootstraponline @sebv :wave: which release will resolve https://github.com/appium/appium/issues/4340 need to include iOS 8 on web view tests