I see the same today. A few directions, lots of "none" rows, and a few more directions.
EDIT: The "none" entries correspond to mileage markers every .1 miles. They've definitely made changes to the response of the RoutingRequest as these "NONE" markers have not existed until very recently. The returned JSON text is significantly longer now, and full of those NONE entries.
EDIT2: The returned code also now includes a "TTS" entry. It looks like Waze is preparing to enable their own navigation list, which should better mirror exactly what the app TTS would read out. There is also a value for "additionalInstruction" which I don't recall seeing before.
EDIT: The "none" entries correspond to mileage markers every .1 miles. They've definitely made changes to the response of the RoutingRequest as these "NONE" markers have not existed until very recently. The returned JSON text is significantly longer now, and full of those NONE entries.
EDIT2: The returned code also now includes a "TTS" entry. It looks like Waze is preparing to enable their own navigation list, which should better mirror exactly what the app TTS would read out. There is also a value for "additionalInstruction" which I don't recall seeing before.
Re: Livemap Navigation Browser Addon (v0.6)