1480893 - Consider making the browsing context ID a struct rather than an integer

Status: RESOLVED WONTFIX

(Core :: DOM: Core & HTML, task, P3)

Description

[Nika Layzell [:nika] (ni? for response)]

This would make it more clear what the object was, as well as giving easy access to the process which created the object, without changing the size at all. If we make it a IPDL struct, we even get serialization :-). For example, consider:

```
struct BrowsingContextId {
  uint32_t mOrigProcId;
  uint32_t mLocalId;
};
```

In the parent process, we could check when receiving an ID for the first time that the mOrigProcId field actually matched the ID of the process which sent us the ID, so that compromised processes couldn't stomp on other processes IDs.

We can even check that the process which sends us an ID actually knows about each ID which it didn't create itself, otherwise it shouldn't be able to send it to us.

Comment 1

[Neha Kochar [:neha]]

We've decided we won't do this, especially because frontend will need it to be an integer.