It's a shame more and more things are breaking, although it's somewhat expected.
The recent overhaul to the netflix web interface (which actually didn't fix enough in my opinion) did completely break the plugin, and since then we've been relying on a compatibility quirk where pretending we're an old browser seemed to give us basically the previous web ui, however it seems that more and more of that is disappearing.
I agree that the only real path forward is to get into some level of netflix api, web scraping won't really work anymore as an increasing amount of the site is using browser-run js and load-on-demand information, which either can't be done (easily) in kodi, or will be prohibitively slow to use. Either way requires a significant overhaul of the plugin.
We may not have to get netflix's support for this though, perhaps these guys can help:
http://netflixroulette.net/api/
They seem to have show data, although I can't see anything in their current api to use to build menus.
Otherwise it's possible we may be able to reverse engineer the api, there certainly is one and it does appear to be designed as a consistent interface between their servers the the client side ui code.
http://applicative.acm.org/speaker-JafarHusain.html
http://techblog.netflix.com/2013/01/opti...x-api.html
http://techblog.netflix.com/2014/03/the-...tform.html
The widevine issues can be resolved by moving away from my canned chrome userdata to use standard chrome install. If my chome keymapping / exit plugin is needed the end user can install that in their normal chrome and turn off the setting to use the canned userdata. Longer term it would probably be better to move netflixbmc away from ChromeDriver to my new webdriver plugin (
https://github.com/andrewleech/script.module.webdriver) which is almost at initial release, which handles key forwarding in a much more compatible way, and doesn't need anywhere near the same amount of hacks to bring chrome to the front. It's not quite ready yet though.
The SSL issues could possibly be fixed by more intelligent automatic testing and switching on/off the advanced ssl depending on what works for the individual connection.
Longer term I'd prefer to stop using python/requests to get the web data and instead use a background web browser (via my script.module.webdriver module) to improve compatibility with modern websites and bring in possibility of leveraging said browser to handle front-end javascript for the page being scraped.
The big issue here for me I haven't been using netflix for some time; I basically stopped finding things I wanted to watch on it.
As such maintaining this plugin is not very near the top of my priority list sad to say. I'll be able to do a bit here and there but can't justify a major rewrite.
FWIW top of my list for kodi is SBS ondemand (australia only) and Hulu, both of which will be using my script.module.webdriver for playback.