Changes between Initial Version and Version 1 of Ticket #278, comment 9


Ignore:
Timestamp:
10/21/2014 03:17:24 PM (6 years ago)
Author:
sebastian
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #278, comment 9

    initial v1  
    11Replying to [comment:4 trev]: 
    2 > It might make sense to change the `prefs.js` implementation for Chrome to use the storage API in general. We cache prefs anyway so we should be able to deal with asynchronous APIs here. 
     2> It might make sense to change the `prefs.js` implementation for Chrome to use the storage API in general. 
    33 
    4 I like the idea, since this is how Chrome extensions are supposed to store persistent properties nowadays. But on the other hand, we have to store these data in a different way on Safari, anyway. So this might just over-complicate things. 
     4I like the idea, since this is how Chrome extensions are supposed to store persistent properties nowadays. But on the other hand, on Safari we anyway have to store these data in a different way. So this might just over-complicate things. 
     5 
     6> We cache prefs anyway so we should be able to deal with asynchronous APIs here. 
     7We still won't have access to the prefs during extension startup. But we have to deal with that anyway, also if only using the Managed Storage API for the pre-configured settings. 
    58 
    69> Note that we would need to change required Chrome version to at least 20 - given that Yandex Browser is based on current Chrome versions now this seems fine however.