STREAM_INITIALIZED triggered on manifest update

Created by: siropeich

Environment

• The MPD passes the DASH-IF Conformance Tool on http://dashif.org/conformance.html
• The stream has correct Access-Control-Allow-Origin headers (CORS)
• There are no network errors such as 404s in the browser console when trying to play the stream
• The issue observed is not mentioned on https://github.com/Dash-Industry-Forum/dash.js/wiki/FAQ
• The issue occurs in the latest reference client on http://reference.dashif.org/dash.js/ and not just on my page

• Link to playable MPD files: https://vm2.dashif.org/livesim/mup_30/testpic_2s/Manifest.mpd http://irtdashreference-i.akamaihd.net/dash/live/901161/keepixo1/manifestBR2.mpd
• Dash.js version: 2.6.0
• Browser name/version: Chrome 61
• OS name/version: MacOS El Capitan

Steps to reproduce

Load any stream configured with a manifest update period.

Observed behaviour

STREAM_INITIALIZED event is triggered not only when the stream is ready but when the manifest is reloaded as per configured period. I don't think this is the desired behaviour, as doc states this event is Triggered when the stream is setup and ready.

It seems to follow the same logic as MANIFEST_LOADED event.