When is Non-Persisted HTML5 by Default is avaialble to test
Reported by
srmo...@zynga.com,
Jun 6 2018
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36 Steps to reproduce the problem: 1. Open https://www.chromium.org/flash-roadmap 2. The first item is mentioned like this - Non-Persisted HTML5 by Default (Target: Chrome 68 - July 2018) 3. Today we have received two version releases - Dev version (68.0.3440.15) and Canary version (69.0.3450.0). In both the versions, Non-Persisting HTML5 by default is not mentioned. What is the expected behavior? Could you point us out in which chrome version (dev/Canary/Stable) we can expect Non-Persisted HTML5 by Default for us to test? What went wrong? We would like to get this information on Non-Persisted HTML5 by Default so that we can work on the flows for our flash based product based on the behavior. Did this work before? N/A Chrome version: 66.0.3359.181 Channel: n/a OS Version: Flash Version:
,
Jun 7 2018
we're now aiming to ship this in M69 (chromestatus.com/features/schedule - stable push beginning 4 SEP). this does not impact any other part of the aforementioned schedule on chromium.org/flash-roadmap.
,
Jun 7 2018
,
Jun 7 2018
thanks for the information. Could you also kindly tell in which canary version we can expect this? |
|||
►
Sign in to add a comment |
|||
Comment 1 by dtapu...@chromium.org
, Jun 6 2018Owner: ericde@chromium.org
Status: Assigned (was: Unconfirmed)