17645 2012-06-29 01:57:11 +0000 Define more precisely what the "origin" of the IDBEnvironment is 2013-02-01 23:14:42 +0000 1 1 1 Unclassified WebAppsWG Indexed Database API unspecified PC All RESOLVED FIXED P2 normal --- 1 jonas dave.null annevk eliotgra israelh mike public-webapps public-webapps-bugzilla oldest_to_newest 69524 0 jonas 2012-06-29 01:57:11 +0000 Specifically, we should make it clear that document.domain doesn't affect indexedDB at all. 71333 1 israelh 2012-07-23 21:55:52 +0000 In IE we use the FQDN, protocol, and a GUID to define the db origin. This doesn't include the port number. That means that for http://www.microsoft.com, we’ll use the complete string to define our origin and add a special GUID to it. From that perspective, modifying the values for document.origin will have no impact on our operations. However, I can see how other implementers could've done this differently without affecting the end result. Are you looking for a note like: "The origin of the IDBEnvironment is calculated in part by using the Fully Qualified Domain Name. However, changes to the document.domain attribute won't have any impact this computation." 82409 2 eliotgra 2013-01-31 17:38:07 +0000 Commit #375 Section 3.1.1 now contains: A database's origin is the same as the origin of the document or worker. Each origin has an associated set of databases. and the following note: Note The database origin is not affected by changes to document.domain. 82427 3 annevk 2013-01-31 19:54:44 +0000 Note that origin does include the port, so IE's implementation has a bug if comment 1 is correct. 82489 4 israelh 2013-02-01 23:14:42 +0000 (In reply to comment #3) > Note that origin does include the port, so IE's implementation has a bug if > comment 1 is correct. That is correct. I didn't mean to imply it didn't on my response.