Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upMake PipelineId a pair of PipelineId and Option<SubpageId> #5235
Comments
|
Blocks #5236. |
|
I'll take a stab at this right now |
|
I was thinking something like:
And then have the HTMLIFrameElement code be the one that generates the unique pipeline id, since that would simplify a number of other things in the future. @jdm does that sound reasonable to you? It might hit an unforeseen roadblock, but it sounds like that could work. |
|
@glennw So the iframe would get the window id from the window, and create the new subpage id? That sounds reasonable to me. |
|
Yes, the window_id would be set once on each window creation, and the window would contain the subpage counter (as it does now) which the iframe would query/increment. |
|
FYI, I didn't feel I have the knowledge to complete this right now, so I'm no longer working on it |
|
I can take a look at this one. |
|
I just took a look at the previous PR, and I came across with the usage of the new |
|
In its current form this issue seems to contradict #5241. As far as @KiChjang's question is concerned, my interpretation is as follows. The constellation manages a (bijective) mapping from Assuming you get an answer to your question, will you continue working on this, @KiChjang? |
|
You can go ahead and work on this issue, I have plenty of other stuff on my plate right now. |
|
This is handled a different way now - iframes are able to generate their own PipelineId. |
This would conceivably allow us to move all subpage-related modification out of script and into the constellation, where it arguably belongs.