Specifically, we should make it clear that document.domain doesn't affect indexedDB at all.
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."
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.
Note that origin does include the port, so IE's implementation has a bug if comment 1 is correct.
(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.