Apparently my earlier response got stuck in moderation but for the record this was exactly what I was looking for Anton. Thank you!
Hans On Saturday, March 9, 2024 at 5:12:34 PM UTC-7 Anton Bershanskyi wrote: > Hi Hans, > > > bit of detail about the work currently being done to extract WebSQL. > > You might be interested in this bug > <https://issues.chromium.org/issues/40910849> titled "Delete WebSQL data > after API removal". Also, data deletion will occur only after the actual > API code is deleted, which will take some time. For reference, I looked > into what it would take and came up with this ~18K LOC patch > <https://github.com/chromium/chromium/compare/main...bershanskiy:chromium:flag-web-sql-access> > (and > I'm not done writing tests for it yet!). > > Sincerely, > Anton. > On Saturday, March 9, 2024 at 4:29:36 PM UTC+2 Hans Meyer wrote: > >> > I'm not aware of such polyfil, however I'm not sure why you would need >> one >> >> Ah ok. I misunderstood. This is actually the biggest part of the lift and >> risk in my particular case. There's a ton of nested >> db.transaction()/tx.executeSql() calls that would need to be rewritten and >> the app in some cases relies directly on SQLResultSet. It's messy. >> >> > the user will need to start up browser and load every profile with your >> extension after you publish the extension update but before Chrome 124 >> >> This is my main concern. I understand some of this is inevitable. Just >> trying to think of ways to mitigate data loss given current circumstances. >> >> > There are no guarantees about on-disk files >> >> Understood. Just wondering if there were any engineers or >> engineer-adjacent folks in the thread who were privy to that bit of detail >> about the work currently being done to extract WebSQL. >> >> For now I'm gonna focus on wrapping up the release and hope for a speedy >> CWS approval. >> >> Thanks again Anton. >> >> Cheers, >> Hans >> >> >> >> On Saturday, March 9, 2024 at 4:51:41 AM UTC-7 Anton Bershanskyi wrote: >> >>> Hi Hans, >>> >>> > Am I correct in understanding that there's a polyfil that allows the >>> use of the WebSQL API surface with the WASM-based SQLite port? >>> >>> I'm not aware of such polyfil, however I'm not sure why you would need >>> one, considering the similarity of the WebSQL API and WASM port: both are >>> merely wrappers for SQLite 3, so you would just need to change the >>> initialization code to talk to WASM wrapper instead of >>> window.openDatabase(). >>> >>> > I'm a little confused about the necessity for and distinction between >>> the two separate releases. ... I will have the new release ready to submit >>> to CWS by this Tuesday >>> >>> I just proposed this as a way to speed up migration, but since you >>> already have a WebSQL-free version ready already, you probably can just >>> release that. >>> >>> > Does anyone know if the WebSQL db file itself will remain intact? >>> >>> There are no guarantees about on-disk files since they are not meant to >>> be read or edited manually... But based on past experience, there is >>> usually no rush to clean up old code, so the files might stay there for >>> some time. Again, no guarantees. You can recover this files like so: >>> >>> 1. Go to chrome://profile-internals , find the relevant profile and >>> copy its "Profile Path" >>> 2. Go to that folder and navigate to >>> ./databases/chrome-extension_<your_extension_id>_<number> >>> 3. There will be a file which you can open in any SQLite viewer >>> >>> Also, note the following: in order for user to migrate data, the user >>> will need to start up browser and load every profile with your extension >>> after you publish the extension update but before Chrome 124 is installed. >>> In fact, it is a known issue that when Chrome changes profile data format >>> and deprecates migration code, some profiles do not get migrated because >>> they are used so rarely. >>> >>> Sincerely, >>> Anton. >>> On Saturday, March 9, 2024 at 7:40:02 AM UTC+2 Hans Meyer wrote: >>> >>>> Does anyone know if the WebSQL db file itself will remain intact? >>>> >>>> I'm hoping yes, as that would preserve some manual options for recovery. >>>> >>>> Hans >>>> >>>> >>>> >>>> On Thursday, March 7, 2024 at 2:54:53 PM UTC-7 Anton Bershanskyi wrote: >>>> >>>>> Hi Hans, >>>>> >>>>> It's unfortunate that you find yourself in this situation. I'm not a >>>>> Google or Chromium representative, but official representatives answered >>>>> this exact question before and consistently rejected >>>>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/fWYb6evVA-w/m/0YblyNG7AQAJ> >>>>> >>>>> any further deadline changes. However, you can use SQL in the browser via >>>>> a >>>>> polyfil library (WASM-based SQLite port >>>>> <https://developer.chrome.com/blog/sqlite-wasm-in-the-browser-backed-by-the-origin-private-file-system>). >>>>> >>>>> One can relatively trivially export data from WebSQL into a different >>>>> browser store (e.g., OPFS) and then continue using existing WebSQL code >>>>> via >>>>> the polyfil. If you need help, I can show you how to prepare two >>>>> incremental extension releases which do this: (1) small revision (with >>>>> short review time) which will back up existing data from WebSQL into >>>>> other >>>>> datastore while still using WebSQL for all work and (2) larger revision >>>>> which will use the new datastore and SQLite polyfil with existing WebSQL >>>>> call sites. After this, you won't have any time pressure and will be able >>>>> to work on refactoring code like converting WebSQL schema to a web-native >>>>> storage of your choice. >>>>> >>>>> Sincerely, >>>>> Anton. >>>>> >>>>> >>>>> On Thursday, March 7, 2024 at 10:43:39 PM UTC+2 Hans Meyer wrote: >>>>> >>>>>> Thanks for the explanation Panos. That makes sense. >>>>>> >>>>>> OK so... please forgive me folks. I know this is a crazy thing to >>>>>> ask, I really do, but I need to take the shot. >>>>>> >>>>>> Is there ANY possibility whatsoever that access to the API can be >>>>>> preserved through 124? >>>>>> >>>>>> I've been grinding away for a year on a major extension rewrite that >>>>>> I'll be ready to submit to the Web Store early next week. The upgrade >>>>>> path >>>>>> includes auto migration from Web SQL to IndexedDB. This extension has 1 >>>>>> million users and I'm kind of freaking out about the number of them who >>>>>> will miss the upgrade window and lose their data. >>>>>> >>>>>> I know it's a long shot and this is an 11th hour ask and I'm not >>>>>> special by any means and I could've been more diligent about heeding the >>>>>> deadline... all true... but, well... as embarrassing as it might be, I >>>>>> have >>>>>> to ask. >>>>>> >>>>>> Respectfully, >>>>>> Hans >>>>>> >>>>>> On Tuesday, March 5, 2024 at 11:30:11 AM UTC-7 Panos Astithas wrote: >>>>>> >>>>>>> The difference between the last trial milestone and the end date is >>>>>>> due to the fact that origin trial tokens contain the expiration date by >>>>>>> design. Given that the token needs to expire after the ending milestone >>>>>>> has >>>>>>> passed and given the often lengthy browser update cycle for some users, >>>>>>> we >>>>>>> ended up with a compromise that expects most clients will have been >>>>>>> updated >>>>>>> when the second to next milestone after the ending one has been >>>>>>> released >>>>>>> (4+4 weeks later). It is really aiming at avoiding the origin trial >>>>>>> feature >>>>>>> being prematurely unavailable to users. >>>>>>> >>>>>>> Granted this is not very obvious, but it has worked reasonably well >>>>>>> in practice. >>>>>>> >>>>>>> Thanks, >>>>>>> Panos >>>>>>> >>>>>>> On Sun, Mar 3, 2024 at 11:35 AM Hans Meyer <ma...@hansmeyer.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Fair enough Anton. Admittedly a bit of wishful thinking on my part. >>>>>>>> >>>>>>>> Although FWIW, the origin trial status in dev tools only mentions >>>>>>>> the expiration date, not version. By no means an excuse, but I'm >>>>>>>> curious, >>>>>>>> why express the trial expiration in terms of a date at all, much less >>>>>>>> a >>>>>>>> date that is 1.5 months after from when it effectively ends for most >>>>>>>> users? >>>>>>>> >>>>>>>> Again, no excuses. I agree the versioning was clearly communicated. >>>>>>>> Just wanted to give some feedback to consider to possibly minimize >>>>>>>> confusion in the future. >>>>>>>> >>>>>>>> Thanks for your response, >>>>>>>> Hans >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Sunday, March 3, 2024 at 10:50:43 AM UTC-7 Anton Bershanskyi >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi Hans, >>>>>>>>> >>>>>>>>> Could you please clarify which web page suggests that the WebSQL >>>>>>>>> availability would extend to Chrome 124 inclusive? All news/articles >>>>>>>>> I >>>>>>>>> could find online suggest that the last version supporting WebSQL >>>>>>>>> would be >>>>>>>>> 123: >>>>>>>>> >>>>>>>>> - Feature: Deprecate and Remove WebSQL >>>>>>>>> <https://chromestatus.com/feature/5134293578285056> >>>>>>>>> - Web SQL deprecation timeline updated >>>>>>>>> >>>>>>>>> <https://developer.chrome.com/blog/web-sql-deprecation-timeline-updated> >>>>>>>>> (the >>>>>>>>> date for Chromium 123 is odd in this one) >>>>>>>>> - Deprecating and removing Web SQL >>>>>>>>> <https://developer.chrome.com/blog/deprecating-web-sql> >>>>>>>>> >>>>>>>>> Also, the DevTools UI already removed WebSQL viewer from >>>>>>>>> "Application" tab. >>>>>>>>> <https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5335172> >>>>>>>>> >>>>>>>>> The change will arrive in Chrome Canary next week. WebSQL flag is >>>>>>>>> also >>>>>>>>> considered to be expired >>>>>>>>> <https://issuetracker.google.com/issues/325834723> (no longer >>>>>>>>> available and will be removed from source code soon). >>>>>>>>> >>>>>>>>> Sincerely, >>>>>>>>> Anton. >>>>>>>>> On Sunday, March 3, 2024 at 5:21:18 PM UTC+2 Hans Meyer wrote: >>>>>>>>> >>>>>>>>>> Hi Ayu, >>>>>>>>>> >>>>>>>>>> Can you clarify... are you saying the deprecation trial does NOT >>>>>>>>>> extend to Chrome 124? I would not have expected that given that the >>>>>>>>>> trial's >>>>>>>>>> expiration date has been communicated consistently as *May 28, >>>>>>>>>> 2024*. >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> Hans >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Friday, February 23, 2024 at 11:15:46 AM UTC-7 Ayu Ishii wrote: >>>>>>>>>> >>>>>>>>>>> Hi Antonio, >>>>>>>>>>> >>>>>>>>>>> That is correct, 123 will be the last supported version via flag >>>>>>>>>>> or policy. >>>>>>>>>>> 124 will be the first version WebSQL will no longer be available >>>>>>>>>>> even with a flag or policy. >>>>>>>>>>> >>>>>>>>>>> Best, >>>>>>>>>>> Ayu >>>>>>>>>>> >>>>>>>>>>> On Friday, February 23, 2024 at 8:02:48 AM UTC-8 Antonio MORENO >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi all, >>>>>>>>>>>> >>>>>>>>>>>> Related to this topic, a bit of a simple question: In the >>>>>>>>>>>> initial announcement, it seemed to indicate that Chrome 123 would >>>>>>>>>>>> be the >>>>>>>>>>>> first version without any kind of support for WebSQL. However, at >>>>>>>>>>>> least in >>>>>>>>>>>> the current version of the beta (123.0.6312.4) support is still >>>>>>>>>>>> there, and >>>>>>>>>>>> can be enabled with the corresponding flag. Can you confirm if >>>>>>>>>>>> this will be >>>>>>>>>>>> the case with the stable version of 123, and the feature will be >>>>>>>>>>>> removed >>>>>>>>>>>> only in version 124? >>>>>>>>>>>> >>>>>>>>>>>> Thanks, and regards, >>>>>>>>>>>> >>>>>>>>>>>> Antonio. >>>>>>>>>>>> >>>>>>>>>>>> On Tuesday, February 13, 2024 at 11:24:34 AM UTC+1 Etienne Noël >>>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi, >>>>>>>>>>>>> >>>>>>>>>>>>> We have been communicating this deprecation for a while now so >>>>>>>>>>>>> unfortunately, we will not extend it further. >>>>>>>>>>>>> >>>>>>>>>>>>> It’s a significant source of security issues so we will keep >>>>>>>>>>>>> the original deprecation timeline. >>>>>>>>>>>>> >>>>>>>>>>>>> If that can be useful to your situation, SQLite is available >>>>>>>>>>>>> in the browser: >>>>>>>>>>>>> >>>>>>>>>>>>> https://developer.chrome.com/blog/sqlite-wasm-in-the-browser-backed-by-the-origin-private-file-system >>>>>>>>>>>>> >>>>>>>>>>>>> It might make the migration easier for you if that’s a >>>>>>>>>>>>> suitable solution. >>>>>>>>>>>>> >>>>>>>>>>>>> Thank you, >>>>>>>>>>>>> >>>>>>>>>>>>> Etienne >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Etienne Noël >>>>>>>>>>>>> >>>>>>>>>>>>> Engineering Manager >>>>>>>>>>>>> >>>>>>>>>>>>> Chrome Storage >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Mon, Feb 12, 2024 at 16:56 Bobby Langley < >>>>>>>>>>>>> rlan...@grubbrr.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Just started using the origin trial in one of our apps that >>>>>>>>>>>>>> requires a slightly overly extertive lift to change from webSQL >>>>>>>>>>>>>> to >>>>>>>>>>>>>> IndexedDB. The expiry says May 28, 2024 -- what is the potential >>>>>>>>>>>>>> that date >>>>>>>>>>>>>> could be extended while we work to release our new version? >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Friday, September 8, 2023 at 4:24:25 PM UTC-4 Panos >>>>>>>>>>>>>> Astithas wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi Guillem, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> The page load limit only applies to trials that introduce >>>>>>>>>>>>>>> new features, not deprecation trials like this one that remove >>>>>>>>>>>>>>> a feature. >>>>>>>>>>>>>>> Apologies for the confusion. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>>> Panos >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Thu, Sep 7, 2023 at 10:29 AM 'Guillem Olivé' via >>>>>>>>>>>>>>> blink-dev <blin...@chromium.org> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I am working by a third-party enterprise and we are still >>>>>>>>>>>>>>>> using webSQL functionality. Our application will be refactored >>>>>>>>>>>>>>>> to remove >>>>>>>>>>>>>>>> it, but it will take some time to make it possible. >>>>>>>>>>>>>>>> We are apprehensive about the disclaimer in the WebSQL >>>>>>>>>>>>>>>> Deprecation Trial registration: "I understand that I may need >>>>>>>>>>>>>>>> to limit use >>>>>>>>>>>>>>>> of this experimental feature to some subset of my users >>>>>>>>>>>>>>>> because of the >>>>>>>>>>>>>>>> limit whereby an experimental feature will be disabled if it >>>>>>>>>>>>>>>> is used on >>>>>>>>>>>>>>>> more than 0.5% of Chrome page loads (as a median over a 14 day >>>>>>>>>>>>>>>> period).". >>>>>>>>>>>>>>>> Will our production application not be able to work if the >>>>>>>>>>>>>>>> overall usage >>>>>>>>>>>>>>>> increases from 0.34% to 0.51% of page loads? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Thanks! >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> El dia dijous, 13 de juliol de 2023 a les 1:59:41 UTC+2, >>>>>>>>>>>>>>>> Ayu Ishii va escriure: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> WebSQL Deprecation Trial registration is now available at >>>>>>>>>>>>>>>>> https://developer.chrome.com/origintrials/#/view_trial/494270059103911937 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Friday, June 30, 2023 at 6:48:09 AM UTC-7 >>>>>>>>>>>>>>>>> tste...@google.com wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Timeline updated in developer-facing comms: >>>>>>>>>>>>>>>>>> https://github.com/GoogleChrome/developer.chrome.com/pull/6725 >>>>>>>>>>>>>>>>>> . >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Mon, Jun 26, 2023 at 10:57 PM Ayu Ishii < >>>>>>>>>>>>>>>>>> ay...@chromium.org> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Hi blink owners, >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> With request from partners, we are planning to update >>>>>>>>>>>>>>>>>>> the timeline to enable deprecation trial from M117 >>>>>>>>>>>>>>>>>>> (previously M118) to >>>>>>>>>>>>>>>>>>> provide a larger window to integrate with the trial before >>>>>>>>>>>>>>>>>>> full removal in >>>>>>>>>>>>>>>>>>> M119. >>>>>>>>>>>>>>>>>>> The rest of the timeline will stay the same. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> NEW - Target timeline: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> M101 - 123 - Enterprise Policy >>>>>>>>>>>>>>>>>>> <https://chromeenterprise.google/policies/#WebSQLAccess> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> M115 - Add deprecation message >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> M117-123 - Deprecation trial >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> M119 - Ship removal OLD - Target timeline: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> M101 - 123 - Enterprise Policy >>>>>>>>>>>>>>>>>>> <https://chromeenterprise.google/policies/#WebSQLAccess> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> M115 - Add deprecation message >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> M118-123 - Deprecation trial >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> M119 - Ship removal >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Thanks, Ayu >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Tuesday, May 16, 2023 at 1:36:24 AM UTC-7 >>>>>>>>>>>>>>>>>>> tste...@google.com wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> On Tue, May 16, 2023 at 10:29 AM Asier Lostalé < >>>>>>>>>>>>>>>>>>>> asier....@openbravo.com> wrote: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Hi Thomas, >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Thanks for your reply. >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> If possible, I'd like to clarify a couple of topics: >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> - I see there is already an "Allows access to WebSQL >>>>>>>>>>>>>>>>>>>>> APIs" flag that can be used to force access to WebSQL. >>>>>>>>>>>>>>>>>>>>> For how long is this >>>>>>>>>>>>>>>>>>>>> flag planned to be kept? Will it be available from M119 >>>>>>>>>>>>>>>>>>>>> to M123? What about >>>>>>>>>>>>>>>>>>>>> after M123? >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Since the code is going to be removed, the flag will be >>>>>>>>>>>>>>>>>>>> removed as a consequence as well. Given the current >>>>>>>>>>>>>>>>>>>> timeline >>>>>>>>>>>>>>>>>>>> <https://developer.chrome.com/blog/web-sql-deprecation-timeline-updated/>, >>>>>>>>>>>>>>>>>>>> I >>>>>>>>>>>>>>>>>>>> would *not* count for the code to exist after 123. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> - As a site owner, how can I take part of the >>>>>>>>>>>>>>>>>>>>> deprecation trial? >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Please see this article on origin trials >>>>>>>>>>>>>>>>>>>> <https://developer.chrome.com/docs/web-platform/origin-trials/#deprecation-trials>. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> A deprecation trial works just the other way round: rather >>>>>>>>>>>>>>>>>>>> than granting >>>>>>>>>>>>>>>>>>>> your site early access to a future feature, it grants you >>>>>>>>>>>>>>>>>>>> late access to a >>>>>>>>>>>>>>>>>>>> past feature. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>>>>>>>> Tom >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>> Thomas Steiner, PhD—Developer Relations Engineer ( >>>>>>>>>>>>>>>>>> https://blog.tomayac.com, https://twitter.com/tomayac) >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Google Germany GmbH, ABC-Str. 19, 20354 Hamburg, Germany >>>>>>>>>>>>>>>>>> <https://www.google.com/maps/search/ABC-Str.+19,+20354+Hamburg,+Germany?entry=gmail&source=g> >>>>>>>>>>>>>>>>>> Geschäftsführer: Paul Manicle, Liana Sebastian >>>>>>>>>>>>>>>>>> Registergericht und -nummer: Hamburg, HRB 86891 >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> ----- BEGIN PGP SIGNATURE ----- >>>>>>>>>>>>>>>>>> Version: GnuPG v2.3.4 (GNU/Linux) >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> iFy0uwAntT0bE3xtRa5AfeCheCkthAtTh3reSabiGbl0ck0fjumBl3DCharaCTersAttH3b0ttom. >>>>>>>>>>>>>>>>>> hTtPs://xKcd.cOm/1181/ >>>>>>>>>>>>>>>>>> ----- END PGP SIGNATURE ----- >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> You received this message because you are subscribed to the >>>>>>>>>>>>>>>> Google Groups "blink-dev" group. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> To unsubscribe from this group and stop receiving emails >>>>>>>>>>>>>>>> from it, send an email to blink-dev+...@chromium.org. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> To view this discussion on the web visit >>>>>>>>>>>>>>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/27f5849e-4762-484d-8afc-80e31692b2f7n%40chromium.org >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/27f5849e-4762-484d-8afc-80e31692b2f7n%40chromium.org?utm_medium=email&utm_source=footer> >>>>>>>>>>>>>>>> . >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>> You received this message because you are subscribed to the >>>>>>>>>>>>>> Google Groups "blink-dev" group. >>>>>>>>>>>>>> To unsubscribe from this group and stop receiving emails from >>>>>>>>>>>>>> it, send an email to blink-dev+...@chromium.org. >>>>>>>>>>>>>> >>>>>>>>>>>>> To view this discussion on the web visit >>>>>>>>>>>>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/0e18aeea-aff4-454e-960e-d350edd0d2b7n%40chromium.org >>>>>>>>>>>>>> >>>>>>>>>>>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/0e18aeea-aff4-454e-960e-d350edd0d2b7n%40chromium.org?utm_medium=email&utm_source=footer> >>>>>>>>>>>>>> . >>>>>>>>>>>>>> >>>>>>>>>>>>> -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/84e22042-2bb0-44bb-aafc-658895ebac83n%40chromium.org.
