Imagine having two tabs open in chrome. They are both open on youtube.com. They are signed into two different youtube accounts with different cookies simultaneously.
This is the experience offered by sessionbox.io in tabbed session management. I'm just wondering how this is possible? No cookies are stored or accessible in my local storage or cookie storage (inspect element in tab or extension).
My question:
How are the different cookies managed in the tabs to create two different session experiences?
Related
In my current chrome extension, I have a popup that has settings for content a content script it uses. I want to be able to save these user settings and have them synced up across devices (different browsers but same user).
I also have my extension connected to a server which has access to a database. Should I create my own login system to save these settings across devices? Or is there a better way to approach this.
I found documentation on OAuth, but there is not much information on if the user tokens are permanent or not, or how effective this would be for the features I am looking for.
When I was deleting data from my Chrome's history, it said it is deleting synced data. I wonder in which sense it is synced? Can you explain a little bit about it?
From what I have read:
Data synchronization technologies are designed to synchronize a single set of data between two or more devices, automatically copying changes back and forth.
Data in your Chrome browser (such as browsing history, saved passwords etc.) is synchronized with your Google account if you set it up. It meant that it was removing such data which was copied to your Google account.
Google's Chrome Web browser allows you to sync data between Chrome browsers on different computers and devices. So the history from all your devices using chrome and logged in with the same account will be deleted. You can disable sync from settings -> advanced sync settings.
I have read about how I can actually drag something from the desktop (from the operating system) to a html5 web page and it can "know" about what I am throwing at it. For example imgur for images. What other ways of interaction between html5 and a system exist.
Not a lot. Any interaction such as the one you've mentioned are those which are initiated by the user. For instance the FileReader API can only read files that the user has selected/dragged.
This is to keep the browser sandboxed so that malicious websites can not tamper with one's machine or files. However html5 gives you:
Geo-location Api lets you physically locate you're machine.
Local Storage is another new feature of html5 which lets you store a small amount of data on the user's machine. It's different from Cookies in that it has a larger space than cookies and the data isn't sent back to the server with every request.
Yes, HTML 5 supports native drag and drop:
http://dev.w3.org/html5/spec/dnd.html
If you peruse the link, you can also see "what other" things HTML 5 can do.
Curious if anyone's seen/heard anything on the ability to use Chrome Profiles to allow synchronization of data contained within extensions between computers.
Put another way, I would like the ability to synchronize / access localStorage from multiple computers signed in with the same browser profile.
Nothing from Google on this now, AFAIK. Anyone know any differnetly?
Chrome has an experimental API that allows syncing of data. Hopefully it will be in stable within the next couple of months.
I've started looking into HTML web database storage for some Chrome extension I'm working on, and it made me wonder - Who should be cleaning abandoned web databases? As opposed to desktop apps, there's no uninstaller for a web site. And as opposed to regular cookies, web databases can be much larger than just 4KB.
I can imagine some browsers or addons might give advanced users a way to clean up locally stored data, but I can't imagine my parents doing that. What will prevent web sites from clogging their hard drive once this feature is commonly used? Is there any way honest and responsible web sites can have their local data removed once they are not used anymore?
On the two websites and 4 apps I use html5 local storage in, I offer an option somewhere (off the About page, or in account settings, or a link at the bottom of the page) which gives you the ability to remove the local database and key-value pairs, as well as the option to opt-out of the site using it.
It'll be persistent, just like cookies. The difference with cookies is that you can store much more data and no expire date can be given.
Firefox has an option to clean those information automatically (Offline storage)